From: Alex Buell <alex.buell@munted.org.uk>
To: David Miller <davem@davemloft.net>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Using s3virge card in Sun Blade 2000
Date: Tue, 04 Jan 2011 20:11:17 +0000 [thread overview]
Message-ID: <1294171877.17576.24.camel@lithium> (raw)
In-Reply-To: <20110104.092637.226761806.davem@davemloft.net>
On Tue, 2011-01-04 at 09:26 -0800, David Miller wrote:
> From: Alex Buell <alex.buell@munted.org.uk>
> Date: Tue, 04 Jan 2011 15:57:07 +0000
>
> > On Mon, 2011-01-03 at 14:36 -0800, David Miller wrote:
> >> From: Alex Buell <alex.buell@munted.org.uk>
> >> Date: Mon, 03 Jan 2011 21:36:13 +0000
> >>
> >> > Those are 32 bit addresses, so I suppose I should be getting the base
> >> > address for the registers accesses from region 1, right?
> >>
> >> Yes, and pre-computed addresses exist in pci_region_start(pdev, 1).
> >
> > Do you have any tips for reducing the amount of reboots I have to do
> > whenever I try loading the s3fb module after changing code?
>
> You should build s3fb as a module, block it from auto-loading in
> /etc/modules.conf, and then load it explicitly by hand as you
> make changes and recompile.
I'm already doing that. In the instances where it results in a crash and
reboots are impossible, dropping into the OpenPROM results in a total
system freeze, cannot type anything in, this means a big red switch
time. Solaris didn't have this problem. Any ideas why Linux does this to
the OpenPROM?
--
Tactical Nuclear Kittens
next prev parent reply other threads:[~2011-01-04 20:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 16:32 Using s3virge card in Sun Blade 2000 Alex Buell
2011-01-03 18:58 ` David Miller
2011-01-03 18:58 ` David Miller
2011-01-03 19:39 ` Alex Buell
2011-01-03 19:43 ` David Miller
2011-01-03 19:43 ` David Miller
2011-01-03 20:33 ` Alex Buell
2011-01-03 20:39 ` David Miller
2011-01-03 20:39 ` David Miller
2011-01-03 21:36 ` Alex Buell
2011-01-03 21:36 ` Alex Buell
2011-01-03 22:36 ` David Miller
2011-01-03 22:36 ` David Miller
2011-01-04 15:57 ` Alex Buell
2011-01-04 17:26 ` David Miller
2011-01-04 17:26 ` David Miller
2011-01-04 20:11 ` Alex Buell [this message]
2011-01-04 20:19 ` David Miller
2011-01-04 20:19 ` David Miller
2011-01-04 20:38 ` Alex Buell
2011-01-05 19:07 ` David Miller
2011-01-05 19:07 ` David Miller
2011-01-05 21:13 ` Alex Buell
2011-01-06 0:33 ` Alex Buell
2011-01-06 20:42 ` Francois Romieu
2011-01-06 20:42 ` Francois Romieu
2011-01-06 20:50 ` Alex Buell
2011-01-06 22:24 ` Alex Buell
2011-01-06 22:29 ` David Miller
2011-01-06 22:29 ` David Miller
2011-01-06 23:25 ` Alex Buell
2011-01-06 23:25 ` Alex Buell
2011-01-06 23:34 ` Alex Buell
2011-01-03 20:37 ` Dave Airlie
2011-01-03 20:37 ` Dave Airlie
2011-01-05 20:37 ` Geert Uytterhoeven
2011-01-05 20:37 ` Geert Uytterhoeven
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=1294171877.17576.24.camel@lithium \
--to=alex.buell@munted.org.uk \
--cc=davem@davemloft.net \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.