Re: FireWire Device Driver

[Katsushi Kobayashi]

Andrew, I am sorry I have lost private mail from you (I just found it in my Mbox), and I am admitted your comments in hackers by other people. I have once proposed my firewire code to merrge -current. And a lot of problems are pointed out. Almost problems will be resolved by code clarification work and it is not difficult. The most important issue pointed out is, the firewire code have to accords "newbus" archtecture and we have to define the firewire specific part. I have not updated the latest code published in ftp site I announced, because I have not a enough time right now to maintain it, and I am investigating bus architecture. If you would like to update my code, I am welcome to new cooperator. If you thought to write another implementation, I am OK. Thanks, "Andrew R. Reiter" wrote: > > hihi. > > I was reading back emails of -hackers from like july '99 and a guy from > Japan had been working on a very promising FireWire device driver ... > Anyway, the other night I had picked up a really awesome book that goes > into detail on FireWire and had basically decided to work on it myself > (until I realized someone had already started work on it!)... However, the > last email that was seemingly sent regarding this issue was one by jkh in > which he gives a major value for the device driver,... and asks when it > should be ready for use with -current. I have emailed the guy from japan > and have received no response... so I am wondering if anyone else knows > what's up with the firewire situation and whether I should go ahead and > pick up work on it? > > Andrew > > *-------------................................................. > | Andrew R. Reiter > | [EMAIL PROTECTED] > | "It requires a very unusual mind > | to undertake the analysis of the obvious" -- A.N. Whitehead > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message