Re: Updating USB stack from FBSD 8.x and others

2009-12-17 Thread nntp.dragonflybsd.org
We are going to end up doing a lot of damage to the real code as is, I've 
been
busy with other things for a while, but just looking at the FreeBSD code has 
reminded
me of just how far we have come. It also reminds me of just how much further 
we need to go


Robgar

"Alex Hornung"  wrote in message 
news:10fba67b0912120726u23e1233awb81cbda04cf...@mail.gmail.com...

I've suggested this a long time ago, and I've also provided some
people with guidance on how to do it, as I've been in contact with the
HPS, the author of usb4bsd.

The main point here is that his i4b repo contains usb4bsd and a
userland wrapper for it. Hence usb4bsd can be elegantly ported to
dragonfly by modifying as little as possible from the real code and
just wrapping it around as his userland wrapper shows. Any attempt to
port this should be aiming for this solution so to avoid a huge mess
and keep the code maintainable.

Cheers,
Alex Hornung



2009/12/12 Alexander Polakov :

2009/12/12, elekktrett...@exemail.com.au :

Hi all,

1) I think we desperately need to bring our USB stack into reality. Is
anyone working on bringing in the new FreeBSD USB code or maybe one from
other BSDs? How difficult would it be? Lets dicuss.


I am going to port FreeBSD 8 stack.





Re: mount nfs from freebsd 7: protocol not supported

2009-12-17 Thread elekktretterr
> Now that you have it working, if you are doing more then just
> playing a bit with it please be sure to use a TCP mount and
> not a UDP mount.  Particularly between FreeBSD 7 and any
> recent DragonFly.  A DragonFly client is capable of queueing
> upwards of 50+ RPCs to the server concurrently and UDP mounts
> will blow up (basically throw data away due to the socket buffers
> not being anywhere near large enough, causing stalls).

The DragonFly box is the server, and Ive forced the FBSD nfs clients to
use TCP.

Is this the right setup?

Petr