[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <732137.54230.qm@web180303.mail.gq1.yahoo.com>
Date: Fri, 13 Aug 2010 06:42:32 -0700 (PDT)
From: David Brownell <david-b@...bell.net>
To: mfuzzey@...il.com, Oliver Neukum <oneukum@...e.de>
Cc: Matthieu CASTET <matthieu.castet@...rot.com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Gary King <GKing@...dia.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-usb <linux-usb@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Greg KH <greg@...ah.com>
Subject: Re: Problem with non aligned DMA in usbnet on ARM
> Subject: Re: Problem with non aligned DMA in usbnet on ARM
I remain unconvinced the bug is anywhere except
in whatever host controller is rejecting the
buffers it's given.
Does anyone have proof the bug is elsewhere?
Think for a moment what chaos the kernel would be
if arbitrary subsystems were allowed to introduce
random DMA alignment "requirements". It would not
be possible to pass buffers between subsystems with
any success at all...
> > 1) Require that usb drivers submit buffers obtained
> from kmalloc() and > friends
Requirements are already documented with the
Description of what memory is DMA-able. It's
not kmalloc() specifically that's required.
with no extra offsets.
Offsets have nothing to do with being DMA-able.
They might have to do with working around hardware
flaws though. (ISTR PXA255 also had a 32-bit goof,
making its DMA engine unusable for most purposes.)
> > 2) Require that usb_submit_urb() accept byte aligned buffers.
I believe we already require that. Of course,
the requirement is on HCDs, not on that call.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists