Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday



On Fri, Aug 1, 2008 at 6:44 AM, Ed Schouten <ed@xxxxxxxx> wrote:
Hello Peter,

* Peter Jeremy <peterjeremy@xxxxxxxxxxxxxxxx> wrote:
On 2008-Aug-01 12:53:18 +0000, Poul-Henning Kamp <phk@xxxxxxxxxxxxxx> wrote:
I got a syntax error on this email Peter, didn't you mean to write:

"Great work Ed, let me send you some patches"

I would love to be able to send some patches. In order to do so, I
need some information about how to interface with the MPSAFE TTY
subsystem and how to adapt an existing driver. I am not the only
person to have indicated a need for some hand-holding and I was under
the impression that Ed would provide this but, to date, all I have is
suggestions to look at patched drivers.

I guess things went wrong, because I probably confused you with Peter
Wemm (I know - I'm bad with names), who inquired about si(4). I did send
him a message some time ago, to see if we could make an appointment to
discuss how we could get si(4) working.

Even though I agree with you that we need more documentation on the TTY
layer's internals, my opinion is that other people should have shown
more interest from the start. When I sent a message a couple of weeks
ago, I almost immediately got a response from Alexander Kabaev (kan@).
He wanted to help me with the dcons(4) driver, which he did. I just
said: take a look at what I did to uart(4) and the console drivers and
gave him some random advice. He was able to send me an almost flawless
diff in a matter of hours, which he committed to the mpsafetty branch
himself!

Maybe I'm replying to too many messages at the same time, but as John
said, it's a lot easier making the remaining drivers work after the code
has been integrated. It's not like we're permanently carving things into
stone - we've almost got a full year to get it all working again.

I'll be happy to work on si(4) once the code hits the tree. Don't let
si(4) get in the way. I have actual hardware (and use it 24x7), so
I've got some incentive.

--
Peter Wemm - peter@xxxxxxxx; peter@xxxxxxxxxxx; peter@xxxxxxxxxxxxx; KI6FJV
"All of this is for nothing if we don't go to the stars" - JMS/B5
"If Java had true garbage collection, most programs would delete
themselves upon execution." -- Robert Sewell
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday
    ... I would love to be able to send some patches. ... need some information about how to interface with the MPSAFE TTY ... suggestions to look at patched drivers. ... him a message some time ago, to see if we could make an appointment to ...
    (freebsd-arch)
  • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday
    ... I would love to be able to send some patches. ... need some information about how to interface with the MPSAFE TTY ... suggestions to look at patched drivers. ... him a message some time ago, to see if we could make an appointment to ...
    (freebsd-current)
  • Re: pull request: wireless-next-2.6 2009-10-28
    ... The rt2x00 drivers include _all_ drivers in the ... If you are not willing to stand behind your own patches, ... the complainer and in that case I will explain to that person _why_ I disagree. ... I meant rt2800 support specifically, sorry if this was not clear. ...
    (Linux-Kernel)
  • Re: pull request: wireless-next-2.6 2009-10-28
    ... The rt2x00 drivers include _all_ drivers in the ... I am not talking about Ralink support I am talking about RT2X00 support. ... I am sending patches upstream, but apparently I don't stand behind them? ... the complainer and in that case I will explain to that person _why_ I disagree. ...
    (Linux-Kernel)
  • Re: Reminder: non-mpsafetty drivers to be *dis*connected on Sunday
    ... I would love to be able to send some patches. ... need some information about how to interface with the MPSAFE TTY ... suggestions to look at patched drivers. ... I'll be happy to work on sionce the code hits the tree. ...
    (freebsd-current)

Loading