From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Christian Suder <csuder@cisco.com>
Cc: sven.cronenberg@web.de, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PALinux on HP9000/735-125
Date: Sun, 6 Jan 2002 23:29:08 +0100 [thread overview]
Message-ID: <20020106232908.B19425@solo.franken.de> (raw)
In-Reply-To: <20020106133432.08684bb1.csuder@cisco.com>; from csuder@cisco.com on Sun, Jan 06, 2002 at 01:34:32PM -0800
On Sun, Jan 06, 2002 at 01:34:32PM -0800, Christian Suder wrote:
> I think it should work to boot HPUX, get the correct EISA .cfg file and
> use the eisa_config utility. The configuration is actually stored in an
but that's not enough. I did that and setup the card with HPUX, but it's
still unconfigured, when Linux finds it. The .cfg describes how to
configure the different card parameters, eisa_config puts the selected
params to a nvram, and some other part does the real card poking
during kernel startup. Other platforms have that card poking stuff
included into the firmware.
It isn't a big deal to do the card setup itself, because .cfg includes
everything needed. It's more a problem of getting that information
during the kernel startup. If we know the nvram setup and how stuff
gets put there, we could read that and do the card setup from within
the Linux kernel. But I haven't found anything about that, yet.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ Alexander Viro on linux-kernel ]
next prev parent reply other threads:[~2002-01-06 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 17:42 [parisc-linux] PALinux on HP9000/735-125 Sven Cronenberg
2002-01-06 18:18 ` Helge Deller
2002-01-06 18:54 ` [parisc-linux] Use the X-Server from HPUX und PALinux? Sven Cronbenberg
2002-01-07 16:35 ` Grant Grundler
2002-01-07 18:01 ` Matt Taggart
2002-01-06 19:13 ` [parisc-linux] PALinux on HP9000/735-125 Thomas Bogendoerfer
2002-01-06 21:34 ` Christian Suder
2002-01-06 22:29 ` Thomas Bogendoerfer [this message]
2002-01-07 0:04 ` nick
2002-01-07 23:34 ` Daniel Engstrom
2002-01-08 1:11 ` Thomas Bogendoerfer
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=20020106232908.B19425@solo.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=csuder@cisco.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=sven.cronenberg@web.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