All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@inwestnet.de>
To: "Brian S. Julin" <bri@mojo.calyx.net>, g@abacus.local
Cc: parisc-linux <parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] HIL_BASE ("finding" devices)
Date: Sun, 12 Mar 2000 22:13:55 +0100	[thread overview]
Message-ID: <20000312221355.H5281@abacus.local> (raw)
In-Reply-To: <Pine.BSO.4.21.0003121544180.20661-100000@mojo.calyx.net>; from bri@mojo.calyx.net on Sun, Mar 12, 2000 at 03:52:52PM -0500

On Sun, Mar 12, 2000 at 03:52:52PM -0500, Brian S. Julin wrote:
> I've only just really started to hack at the HIL driver, but
> one thing I noticed off the bat is that the HIL_BASE defined
> in hil.h is 0xf0821000 while the device base listed when 
> I boot for the HIL is 0xf0201000.  This probably means it 
> varies across different models.

It probably does.   AFAIK, the HIL driver is pretty much a hack
Matthew did to get his 715's keyboard working (the 715 and keyboard
are here now and Matthew is in Ottawa, and I don't have it set up
so didn't work on the driver).

> Optimally I suppose the best thing would be to somehow 
> find the device -- the code that prints out the hardware 
> found seems to get strings from the "pdc" which I glean is
> the "BIOS".  I suppose the only thing the HIL will have that
> is unique is this string, or are there model invariant 
> numbers like the PCI fn?

There are indeed, hversion and sversion are the words you're looking
for.  See the register_driver for the current (broken IMHO) interface.

> Alternatively I suppose we could do what the alpha folk
> have done and have a compile-time selection of the system type
> (e.g. "avanti") which sets the values for various things like that.

No way.  The "machine vector" concept wouldn't work well for us - it
works for ppc and alpha because those machines usually have a relatively
limited number of setups - with most chipsets, you can only use one CPU
type;  Lasi is used with PA7100LC, PA7300LC, PA8000, PA8200, and PA8500,
and shares code with the PA7100 (?) version (ASP) as well.  Furthermore
PDC device detection is sane to a certain extent - a lot of devices PDC
doesn't tell us about though.

	Philipp Rumpf

  reply	other threads:[~2000-03-12 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-11 18:13 [parisc-linux] undefined reference in libgcc.a blacky
2000-03-11 18:22 ` Philipp Rumpf
2000-03-12 20:52 ` [parisc-linux] HIL_BASE ("finding" devices) Brian S. Julin
2000-03-12 21:13   ` Philipp Rumpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-13 15:10 Ulrich Strelow
2000-03-13 16:05 ` Philipp Rumpf

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=20000312221355.H5281@abacus.local \
    --to=prumpf@inwestnet.de \
    --cc=bri@mojo.calyx.net \
    --cc=g@abacus.local \
    --cc=parisc-linux@thepuffingroup.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 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.