From: Woody Suwalski <woodys@xandros.com>
To: Martin Michlmayr <tbm@cyrius.com>, rmk@arm.linux.org.uk
Cc: Ralph Siemsen <ralphs@netwinder.org>,
linux-fbdev-devel@lists.sourceforge.net,
debian-arm@lists.debian.org
Subject: Re: 2.6.16-rc3 + Xorg 6.9.0 - works for me...
Date: Wed, 26 Apr 2006 14:38:34 -0400 [thread overview]
Message-ID: <444FBE2A.90106@xandros.com> (raw)
In-Reply-To: <443F8EB1.30803@netwinder.org>
>>>
I just upgraded my Netwinder from 2.4.27 to 2.6.15 and the framebuffer
no longer works. Console works but when I start X.org I first get a
corrupted screen and a little bit later the whole machine hangs.
There's no panic or any information on the serial console.
<<<
This problem appears only on Cyber2010 chips (Netwinders with Cyber2000
work OK)
The crash issue on 2010 can be solved by disabling burst mode on the
Cyberpro 2010 (graphic register 0x30, EXT_BUS_CTL_PCIBURST_WRITE=0). It
is enabled in the kernel driver by default now.
However, I can see in the cyber2000fb.c file that the 2010 is also used
on Shark architecture.
Martin, Russell,
Can you verify if the current 2.6.1x kernel + X 6.9 works OK on SHARK
machine??? I do not have any of them here to test...
Basically we need to establish, if this fix is needed just for
Netwinders with CyberPro 2010 (here tested on machine with 1M VRAM in
32-bit mode, but Martin seems to have problem on 2M VRAM Netwinder?) or
all machines with CyberPro 2010.
Thanks, Woody
--
Xandros Corporation
Simple. Powerful. Linux.
Visit us at http://www.xandros.com
next parent reply other threads:[~2006-04-26 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43F4AF97.8080909@xandros.com>
[not found] ` <443E3A4B.8000101@netwinder.org>
[not found] ` <443E4435.1060904@xandros.com>
[not found] ` <443F8EB1.30803@netwinder.org>
2006-04-26 18:38 ` Woody Suwalski [this message]
2006-04-26 20:09 ` 2.6.16-rc3 + Xorg 6.9.0 - works for me Russell King
2006-04-26 20:15 ` Woody Suwalski
2006-04-27 11:48 ` Martin Michlmayr
2006-04-27 11:53 ` Russell King
2006-04-27 11:59 ` Martin Michlmayr
2006-04-27 12:23 ` Ralph Siemsen
2006-04-27 12:32 ` Woody Suwalski
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=444FBE2A.90106@xandros.com \
--to=woodys@xandros.com \
--cc=debian-arm@lists.debian.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=ralphs@netwinder.org \
--cc=rmk@arm.linux.org.uk \
--cc=tbm@cyrius.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).