From: Andrew Morton <akpm@osdl.org>
To: James Simmons <jsimmons@infradead.org>
Cc: VANDROVE@vc.cvut.cz, vince@kyllikki.org,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: vga16fb broke
Date: Tue, 18 May 2004 17:38:45 -0700 [thread overview]
Message-ID: <20040518173845.1e03288c.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0405190117430.16503-100000@phoenix.infradead.org>
James Simmons <jsimmons@infradead.org> wrote:
>
>
> > I have pondered your email at length and have failed to understand it.
> >
> > I _think_ you're saying that we need to do this, which will fix x86:
> >
> > --- 25/drivers/video/vga16fb.c~vga16fb-fix Tue May 18 17:10:14 2004
> > +++ 25-akpm/drivers/video/vga16fb.c Tue May 18 17:10:39 2004
> > @@ -1347,7 +1347,7 @@ int __init vga16fb_init(void)
> >
> > /* XXX share VGA_FB_PHYS and I/O region with vgacon and others */
> >
> > - vga16fb.screen_base = ioremap(VGA_MAP_MEM(VGA_FB_PHYS), VGA_FB_PHYS_LEN);
> > + vga16fb.screen_base = VGA_MAP_MEM(VGA_FB_PHYS);
> > if (!vga16fb.screen_base) {
> > printk(KERN_ERR "vga16fb: unable to map device\n");
> > ret = -ENOMEM;
>
> This will make the driver on all platforms.
There's a missing word in that sentence. Was it "work" or "crash"? This
matters ;)
> _
> >
> > and that ARM and others need to teach their VGA_MAP_MEM() to do an internal
> > ioremap().
> >
> > Or do you mean something else? Please be more clear?
>
> I like to see the VGA_MAP_MEM hack go away and be replaced with ioremap.
If you can cut a patch we can ask arch maintainers to review and test it.
next prev parent reply other threads:[~2004-05-19 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040514145559.55202998.akpm@osdl.org>
2004-05-18 22:36 ` vga16fb broke James Simmons
2004-05-19 0:16 ` Andrew Morton
2004-05-19 0:18 ` James Simmons
2004-05-19 0:38 ` Andrew Morton [this message]
2004-05-19 22:09 ` James Simmons
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=20040518173845.1e03288c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vince@kyllikki.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;
as well as URLs for NNTP newsgroup(s).