From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
torvalds@transmeta.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fb.h header fix.
Date: Thu, 05 Feb 2004 10:31:53 +1100 [thread overview]
Message-ID: <1075937512.4029.47.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0402041857210.20659-100000@phoenix.infradead.org>
> > Not yet, it's a ppc64 bug, I haven't had time to fix it, for some
> > reason, ppc64 doesn't have readq/writeq nor __raw_ IO accessors.
>
> This means more than the fbdev layer will break on the ppc64.
> Ben you you post a patch for the ppc64 so the fbdev patch can go in?
Yes, but I think Andrew should still merge your patch at this point,
I'll send the ppc64 fix today hopefully along with other ppc64 io.h
fixes.
Then we need the rest of the core & driver bits in. I'd really like
2.6.3 to be "complete" for PowerMacs (both ppc32 and ppc64) which
means including the fbdev updates. I think the fbdev core changes are
now good enough to get in. I'm fairly sure there are still fbcon bugs
but I'm also sure those are already upstream so they aren't worth
postponing the merge.
Ben.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-04 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 1:12 fb.h header fix James Simmons
2004-02-04 2:03 ` Andrew Morton
2004-02-04 4:13 ` Benjamin Herrenschmidt
2004-02-04 18:58 ` James Simmons
2004-02-04 23:31 ` Benjamin Herrenschmidt [this message]
2004-02-05 18:06 ` 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=1075937512.4029.47.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).