Date: Mon, 20 Dec 1999 14:07:23 +0100 (CET) From: Nick Hibma <n_hibma@webweaving.org> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Bill Paul <wpaul@skynet.ctr.columbia.edu>, hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking Message-ID: <Pine.BSF.4.20.9912201406100.398-100000@localhost> In-Reply-To: <199912200034.QAA03909@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Your register read will take at least 1msec. That is the time between scheduling the transfer and the interrupt being triggered for completion. But typically it will take 2msecs. Nick > > Because this is not an asynchronous task that I'm trying to do here. > > I'm talking about reading and writing registers from the ethernet > > controller. If this was a PCI device, I'd be using > > bus_space_read_X()/bus_space_write_X() to read the registers directly. I > > don't want to start reading a register and then come back a while later > > to read the results. The code isn't meant to work like that. > > Unfortunately, given that your 'register read request' is being queued > over what is basically a packet-switched network, you're going to have to > change the way the code works so that it _can_ work like that. If you > don't like it now, imagine how much less you're going to like, say, I2O > or SystemIO... > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.9912201406100.398-100000>