From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Kronos <kronos@people.it>,
Geert Uytterhoeven <geert@linux-m68k.org>,
DRI Devel <dri-devel@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: New kernel API for ROMs
Date: Sat, 07 Aug 2004 19:51:51 +0100 [thread overview]
Message-ID: <1091904710.18813.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20040807174057.35529.qmail@web14922.mail.yahoo.com>
On Sad, 2004-08-07 at 18:40, Jon Smirl wrote:
> We have to copy the whole thing when the driver tells us to. After we
> copy the ROM the hardware is going to use the address decoder for
> something else. There is no safe way to get back to the ROM again other
> than to unload the device driver.
Good point on mmap not working yes. We can still copy it in 4K chunks to
userspace though not keep it in kernel. The rom boot stuff in the design
is in user space.
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-08-07 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 21:21 New kernel API for ROMs Jon Smirl
2004-08-07 13:16 ` Geert Uytterhoeven
2004-08-07 14:59 ` Jon Smirl
2004-08-07 16:37 ` Kronos
2004-08-07 16:09 ` [Linux-fbdev-devel] " Alan Cox
2004-08-07 17:40 ` Jon Smirl
2004-08-07 18:51 ` Alan Cox [this message]
2004-08-07 16:54 ` [Linux-fbdev-devel] " Jon Smirl
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=1091904710.18813.1.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=geert@linux-m68k.org \
--cc=jonsmirl@yahoo.com \
--cc=kronos@people.it \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).