linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Torrey Hoffman <thoffman@arnor.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] 2.5.70-bk15: RadeonFB dies at boot, and is undocumented
Date: Mon, 16 Jun 2003 21:29:51 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0306140031430.29353-100000@phoenix.infradead.org> (raw)
In-Reply-To: <1055546532.1256.19.camel@torrey.et.myrio.com>


> With the Radeon framebuffer driver compiled in, 2.5.70-bk15 oopses very
> early during the boot process.  The oops is visible in text mode but
> scrolls off the screen.  (I really need to set up a serial console!)

If you see the oops that is good thing. That means the framebuffer driver 
works. 

> [thoffman@torrey fb]$ pwd
> /home/archive/Kernels/linux-2.5.70-bk15/Documentation/fb
> [thoffman@torrey fb]$ grep radeon *
> [thoffman@torrey fb]$ 
> 
> There is not a single mention of the radeon driver under Documentation! 
> Even a 20 line note explaining what the kernel command line format is
> would be nice.

No :-( 

> PS: Mr. Simmons, I really appreciate your work on the framebuffer and
> console subsystem.  To make it easier for people to find you, perhaps a
> little patch to update your email addresses throughout the code would be
> worth while?   A quick grep under drivers/video turns up four different
> addresses in about a dozen files, hopefully I am sending this email to a
> current address:
> 
> jsimmons@users.sf.net
> jsimmons@linux-fbdev.org
> jsimmons@infradead.org
> jsimmons@transvirtual.com

Good point. I will update everything.



      parent reply	other threads:[~2003-06-16 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 23:22 [OOPS] 2.5.70-bk15: RadeonFB dies at boot, and is undocumented Torrey Hoffman
2003-06-14  0:03 ` Greg KH
2003-06-16 18:42   ` Torrey Hoffman
2003-06-16 20:29 ` James Simmons [this message]

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=Pine.LNX.4.44.0306140031430.29353-100000@phoenix.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thoffman@arnor.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).