From: Oliver Neukum <oliver@neukum.org>
Organization: NOvell
To: "Francis Moreau" <francis.moro@gmail.com>
Subject: Re: usb_get_status(): what a weird implementation !
Date: Mon, 30 Jun 2008 15:51:41 +0200
User-Agent: KMail/1.9.9
Cc: "David Brownell" <david-b@pacbell.net>, linux-usb@vger.kernel.org,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <200806261011.00287.oliver@neukum.org> <200806301346.11267.oliver@neukum.org> <38b2ab8a0806300541q756e9b6fl445a5ee69d403ce7@mail.gmail.com>
In-Reply-To: <38b2ab8a0806300541q756e9b6fl445a5ee69d403ce7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200806301551.42252.oliver@neukum.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1117
Lines: 34

Am Montag 30 Juni 2008 14:41:37 schrieb Francis Moreau:
> On Mon, Jun 30, 2008 at 1:46 PM, Oliver Neukum <oliver@neukum.org> wrote:
> > Am Montag 30 Juni 2008 13:04:21 schrieb Francis Moreau:

> >> well, it wouldn't be hard to allocated a buf on the stack with correct
> >> alignement
> >> and size for DMA mapping.
> >
> > Where would you put it and meet the alignment requirements?
> >
> 
> wouldn't this code below do the trick ?
> 
> void foo(void)
> {
>     unsigned char __buf[2 * CACHE_LINE_SIZE];
>     unsigned char *buf;
> 
>     buf = ((unsigned long)__buf) + CACHE_LINE_SIZE-1) & ~(CACHE_LINE_SIZE-1);
> }
> 
> but I agree it looks hackish.

If your buffer is smaller than CACHE_LINE_SIZE it should work.
However, this needs input from people who understand DMA in and out.
But how large is 2 * CACHE_LINE_SIZE compared to the kernel stack?

	Regards
		Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/