linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Rebe" <rene.rebe@gmx.net>
To: James Simmons <jsimmons@transvirtual.com>
Cc: linux-kernel@vger.kernel.org, ademar@conectiva.com.br,
	rolf@sir-wum.de, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: sis630 - help needed debugging in the kernel
Date: Mon, 18 Jun 2001 20:32:03 +0200	[thread overview]
Message-ID: <20010618203203.35390ca8.rene.rebe@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10106170652280.17509-100000@transvirtual.com>
In-Reply-To: <20010616232740.092475e2.rene.rebe@gmx.net> <Pine.LNX.4.10.10106170652280.17509-100000@transvirtual.com>

On Sun, 17 Jun 2001 07:03:55 -0700 (PDT)
James Simmons <jsimmons@transvirtual.com> wrote:

[...]

> Yes. It oops in fbcon_cfb8_putc. I haven't figured out yet what exactly
> caused it. I don't have this card to play with :-( Did you run the other
> test I suggested.

Never arrived here :-(. (Pleas cc me, since I'm not on this lists ...)

> Try booting at 640x480 with a color depth of 32. Then
> try booting at a different resolution (1024x768) at the default color
> depth. I want to see if its a error with the resolution setting or if it
> is a error with setting up the data relating to the color depth handling. 
> The results should give me some clue.

I can't set the videomode for the driver ...? I tried:

video=sis:vesa:0x112
video=sis:xres:640,yres:480,depth:32
video=sis,xres:640,yres:480,depth:32

Is there another way to tell the fb driver what mode to use??

I set the shared memory size from 16MB to 64 MB: results:
  sisfb: framebuffer at 0xe0000000, mapped to 0xc8800000, size 65536k
  sisfb: MMIO at 0xefce0000, mapped to 0xcc801000, size 128k
  Unable to handle kernel paging request at virtual address cc8002e0

old results:
  sisfb: framebuffer at 0xe0000000, mapped to 0xcb800000, size 16384k
  sisfb: MMIO at 0xefce0000, mapped to 0xcc801000, size 128k
  Unable to handle kernel paging request at virtual address cc800180

(Maybe some typo somewhere ??)

PS: I have more free time the next days -> shorter latency and more kernel
source read time ...

k33p h4ck1n6 René

-- 
René Rebe (Registered Linux user: #127875)
http://www.rene.rebe.myokay.net/
-Germany-

Anyone sending unwanted advertising e-mail to this address will be charged
$25 for network traffic and computing time. By extracting my address from
this message or its header, you agree to these terms.

  parent reply	other threads:[~2001-06-18 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 15:23 sis630 - help needed debugging in the kernel René Rebe
2001-06-13 16:54 ` James Simmons
2001-06-16 21:27   ` René Rebe
2001-06-17 14:03     ` James Simmons
2001-06-18 18:32     ` René Rebe [this message]
2001-06-18 19:28       ` Paul Mundt
2001-06-18 21:58         ` James Simmons
2001-06-18 22:02           ` Paul Mundt
2001-06-18 21:01       ` René Rebe
2001-06-13 21:25 ` René Rebe

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=20010618203203.35390ca8.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=ademar@conectiva.com.br \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolf@sir-wum.de \
    /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).