Re: netatm: plan for removal unless an active maintainer is found

In message: <20060315151058.c85pw3x14wkkk8g0@xxxxxxxxxxxxxxxxxxx>
Alexander Leidinger <Alexander@xxxxxxxxxxxxx> writes:
: Robert Watson <rwatson@xxxxxxxxxxx> wrote:
:
: > The other large chunk of non-MPSAFE network device driver and stack
: > code, FYI, is the i4b code. In principle, a newly added committed is
:
: The USB stack is also a part of the problem (USB network interfaces), I
: think.

It definitely is a problem. And I didn't list any usb interfaces as
not being MPSAFE.

: > now available to work on the capi integration, and hopefully will do
: > the SMP safety work as part of that. If not, it's also on the
: > chopping block. It's a significant piece of otherwise unmaintained
: > code, and something that's not trivially testable (at least, not by
: > me or anyone I've talked to lately :-). I don't want to see it leave
: > the tree, but it needs to be updated so that it can run MPSAFE before
: > 7.0.
:
: I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from
: scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have
: tested or reviewed neither of them, but as far as I can read in the
: mailinglists, he adresses not only the issues you mention here, but he also
: provides bugfixes and additional features compared to our current code base.

The problem is that this code isn't busdma safe at the moment. It was
posted for review on the NetBSD lists and this was the biggest set of
comments on tech-kern@xxxxxxxxxxx Since it isn't busdma safe, we'd
lose usb on sparc64 (and maybe arm) when this code is brought into the
tree. There have also been signficant concerns about the locking
that's done in the code as well, but I've not reviewed it recently.

There's been a lot of work done here, and that work is generally good,
but last time I looked at the code it wasn't ready to be integrated to
the tree.

Warner

_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Bug in OHCI2 driver for Windows CE 5.0?
    ... CE's USB stack is not derived from any of the desktop Windows stacks; ... A short packet (i.e., a packet smaller ... I'm in a middle of porting USB device-driver from Windows NT/2k/XP... ... A low-speed device (Contains couple of firmware versions) ...
    (microsoft.public.windowsce.platbuilder)
  • Re: panic when removing pccard
    ... If i insert and then remove a pcmcia card using the ubsa module ... devices by the kernel is not correct. ... If you want to be able to remove the card you need to install the new USB ... The old USB stack is completely broken when it comes to this ...
    (freebsd-current)
  • RE: Spam:Re: USB Host Stack Debugging
    ... I guess it is the 2.2.6 kernel might have had the USB initial USB Stack. ... i.e. Linus initial USB Mouse debugging STACK. ... Mukund Jampala ...
    (Linux-Kernel)
  • Re: [spi-devel-general] Re: [PATCH/RFC] SPI: add DMAUNSAFE analog
    ... allocating it on stack, thus the buffer is not DMA-safe. ... so allocationg it in interrupt context is buggy. ... but it's particularly relevant since both USB and SPI ...
    (Linux-Kernel)