On Mon, 2002-11-25 at 02:59, Mike Rosing wrote: > I'm doing that right now as a matter of fact. I'm using the FTDI chip > and the serial interface so I can use a lot of my legacy code with little > trouble. Only it's been a *lot* of trouble. lol > > If you start with a 2.4.14 kernel or later, you won't have any where near > the problems I've got. My legacy code sits on a 2.2.20 system, and while > that has usb capability, the FTDI driver isn't working right. I tried to > upgrade my kernel to 2.4, and blew a lot of things away. It's taken me 3 > days to recover the 2.2.20 system (at 2 - 3 hours a day, not full time :-) well i've just spent the past week trying to get my firewall up after a HD crash :(
> There's a lot of detail, but it can be made to work. Just how much work > you want to do, and where you want to tie into linux is up to you. It's > wide open to the point where you can write a driver that talks directly to > usbcore or you can work at a much higher level and use the FTDI driver > that's already there. nice so u reckon to use the ftdi stuff rather than writing my own module? I like things the easy way :P regards charles
signature.asc
Description: This is a digitally signed message part
