From: Stelian Pop <stelian@popies.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] meye: correct printk of dma_addr_t
Date: Wed, 4 Feb 2004 09:44:37 +0100 [thread overview]
Message-ID: <20040204084437.GA13455@deep-space-9.dsnet> (raw)
In-Reply-To: <20040203162822.64ee18e1.rddunlap@osdl.org>
On Tue, Feb 03, 2004 at 04:28:22PM -0800, Randy.Dunlap wrote:
> | mchip_ptable[] just contains pointers to kernel memory. It doesn't seem
> | appropriate to be casting these to dma_addr_t's
>
>
> Ugh... if I am reading this correcly, what I see is that
> mchip_table[] is mostly used for kernel pointers, like you say.
Yep. The meye driver uses 256 PAGE_SIZE buffers. The kernel virtual
pointers to these buffers are stored in mchip_ptable[]. The
"toc" containing the dma pointers to these buffers must be given
to the device as a table having 256 entries, each being 32 bits in length.
In the code I used the last entry of mchip_ptable to store the toc,
but I could as well construct a different data structure.
Anyway, the device expects a dma_addr to be 32 bits in length, so this
will not work anyway with HIGHMEM32 (moreover, this is a driver for the
motion eye camera which is found only in C1 Vaio Sony laptops, which
motherboard is limited to 384 MB...).
I can see only two solutions:
*) put the toc in a different, dma_addr_t[] structure, so the
driver will compile even with HIGHMEM32 (but won't work...)
*) exclude meye from kernel config when HIGHMEM32 is set.
Which one do you prefer ?
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2004-02-04 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 23:36 [PATCH] meye: correct printk of dma_addr_t Randy.Dunlap
2004-02-03 23:57 ` Andrew Morton
2004-02-04 0:28 ` Randy.Dunlap
2004-02-04 8:44 ` Stelian Pop [this message]
2004-02-04 16:05 ` Randy.Dunlap
2004-02-05 13:37 ` Stelian Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040204084437.GA13455@deep-space-9.dsnet \
--to=stelian@popies.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox