From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David S. Miller" <davem@redhat.com>,
jsimmons@infradead.org, benh@kernel.crashing.org,
paulus@samba.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: atyfb in 2.5.51
Date: Thu, 12 Dec 2002 21:23:23 +0100 [thread overview]
Message-ID: <20021212202323.GA789@elf.ucw.cz> (raw)
In-Reply-To: <1039642510.18467.40.camel@irongate.swansea.linux.org.uk>
Hi!
> On Wed, 2002-12-11 at 20:43, David S. Miller wrote:
> > fbdev is nice, in the specific cases where the device fits the fbdev
> > model, because once you have the kernel bits you have X support :)
>
> fbdev also can't be used in some situations on x86. Deeply fascinating
> things happen on some x86 processors if you execute a loop of code with
> an instruction that crosses two different memory types.
Sounds like cpu bug to me? What cpus are affected?
Could be worked around by pointing debug register at memory boundary?
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-12-12 20:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 22:31 atyfb in 2.5.51 Paul Mackerras
2002-12-10 23:11 ` Benjamin Herrenschmidt
2002-12-11 6:18 ` James Simmons
2002-12-11 8:42 ` David S. Miller
2002-12-11 15:16 ` James Simmons
2002-12-11 20:43 ` David S. Miller
2002-12-11 21:35 ` Alan Cox
2002-12-12 20:23 ` Pavel Machek [this message]
2002-12-13 8:53 ` Geert Uytterhoeven
2002-12-13 10:26 ` Alan Cox
2002-12-22 13:40 ` Geert Uytterhoeven
2002-12-11 21:06 ` Paul Mackerras
2002-12-15 11:45 ` Stefan Reinauer
2002-12-13 8:49 ` Geert Uytterhoeven
2002-12-11 12:49 ` [Linux-fbdev-devel] " Antonino Daplas
2002-12-11 15:46 ` 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=20021212202323.GA789@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.