On Sun, May 02, 2004 at 10:38:42AM -0400, Rita Lin wrote:
Hello,
I'm writing a USB driver for a device that does not have any interrupt. It only has
Bulk-in and Bulk-out. A periodic polling status from default pipe is required to
have a smooth data transfer. I used timeout() routine to
Well, Don Bowman was very helpful in suggesting some kernel parameters.
Unfortunately, they
did not work for us. If we had the time to experiment with more
settings, perhaps we would have
been able to find the right combination. Since we do not have that time
due to our schedule I was
forced to
On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote:
I found the htonl implemention in libc for i386 is not sync with the
kern.
sys use bswap for swaping the int. but libc still use xchg.
IS THIS LOST?
It's because libc still supports 80386 which doesn't have bswap (introduced on
the 486
But I don't understand the whole issue you have.
Just schedule a request and wait for the device to ack.
The Host controller does the polling for you as long as the request is
queued and the timeout value supplied with the request did not time out.
That has nothing to do with FreeBSD - it's
On Mon, May 03, 2004 at 04:37:22PM -0400, Rita Lin wrote:
But I don't understand the whole issue you have.
Just schedule a request and wait for the device to ack.
The Host controller does the polling for you as long as the request is
queued and the timeout value supplied with the request
Igh - that sounds like a very bad device design then.
There would have been lots a ways to do in a clean way without
additional pipes - such as transfering 0 sized packets to trigger a
status inquiry or by adding status bytes in each packet.
For what purpose do you need to poll the status in
That is what I call a bad design.
You waste resources because the device designer did not take the
features he had available.
Okay, I guess so. There are also other minor things that I don't understand
why
the device is implemented the way it is. Since I don't make it, and I don't
work for
the
On Mon, May 03, 2004 at 08:19:43AM -0700, John Uhlig wrote:
Well, Don Bowman was very helpful in suggesting some kernel parameters.
Unfortunately, they
did not work for us. If we had the time to experiment with more
settings, perhaps we would have
been able to find the right combination.
On Mon, May 03, 2004 at 06:48:14PM -0400, Rita Lin wrote:
That is what I call a bad design.
You waste resources because the device designer did not take the
features he had available.
Okay, I guess so. There are also other minor things that I don't understand
why
the device is implemented
On Tue, May 04, 2004 at 09:04:53AM +0800, Deng XueFeng wrote:
On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote:
I found the htonl implemention in libc for i386 is not sync with the
kern.
sys use bswap for swaping the int. but libc still use xchg.
IS THIS LOST?
It's because
Deng XueFeng wrote this message on Tue, May 04, 2004 at 09:04 +0800:
the 486 IIRC). The kernel only supports 486+ unless you explicitly build an
^^^
80386 kernel, which won't use bswap for htonl().
On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote:
I found the htonl implemention in libc for i386 is not sync with the
kern.
sys use bswap for swaping the int. but libc still use xchg.
IS THIS LOST?
It's because libc still supports 80386 which doesn't have bswap (introduced on
All,
It's time again for bi-monthly status reports. As always, the
template is at http://www.freebsd.org/news/status/report-sample.xml.
Please make submissions to [EMAIL PROTECTED] by May 12 for
inclusion. Any projects that relate to FreeBSD development,
documentation, ports, etc, are welcome.
All,
It's time again for bi-monthly status reports. As always, the
template is at http://www.freebsd.org/news/status/report-sample.xml.
Please make submissions to [EMAIL PROTECTED] by May 12 for inclusion.
Any projects that relate to FreeBSD development, documentation, ports,
etc, are welcome.
On Mon, 3 May 2004, Kevin A. Pieckiel wrote:
I want to modify sys/param.h to increase the value of MAXLOGNAME. I know
I've done exactly this..
edit /usr/src/sys/param.h
cd /usr/src
make includes
now teh sources and the files in /usr/include are in sync
of course you are now incompatible
I want to modify sys/param.h to increase the value of MAXLOGNAME. I know
I'll need to recompile world/kernel after such a change. Do I need to
only modify /usr/src/sys/sys/param.h, or rather do I need to modify
/usr/include/sys/param.h? I'm assuming when I make buildworld or make
buildkernel,
On Mon, May 03, 2004 at 05:36:47PM -0400, Rita Lin wrote:
Igh - that sounds like a very bad device design then.
There would have been lots a ways to do in a clean way without
additional pipes - such as transfering 0 sized packets to trigger a
status inquiry or by adding status bytes in
On Monday 26 April 2004 12:56, Steven Hartland wrote:
Intel still do iirc.
- Original Message -
From: Stephen Hocking
Does anyone know where I can lay my hands on one of those 4 port
ethernet cards that used to be around a while back?
18 matches
Mail list logo
