From: Olaf Hering <olh@suse.de>
To: BenH <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-users@lists.linuxppc.org
Subject: Re: find the OF boot-device
Date: Wed, 2 Feb 2000 00:23:06 +0100 [thread overview]
Message-ID: <20000202002306.A32257@suse.de> (raw)
In-Reply-To: <20000201235557.015906@192.168.1.10>
On Tue, Feb 01, BenH wrote:
> On Tue, Feb 1, 2000, Olaf Hering <olh@suse.de> wrote:
> How do you plan to match the device to the OF node ? I've looked into
> this issue for some time now, but I don't really see a valid way to know
> that a given Linux device (/dev/xxx) corresponds to a given OF node.
> Especially when using PCI SCSI cards. Is there a way from userland to
> retreive PCI infos of a controller from it's /dev/sdXX node ?
It is a little harder. There is no way to see which drive is connected
to a controller. If you have an Adaptec you can parse something in
/proc/scsi/aic78xxx and scsi. The symbios logic driver gives you no
hint. The same problem with the IDE drives.
But what do we really need?
OF can only boot from known devices, I can't boot from an old adaptec
2940 or any symbios logic adapter.
And if you have an PCI IDE controller then the OF won't boot from
that unknown device.
This reduces the possible boot-devices:
We can boot from some Adaptec controllers, we can boot from every IDE
drive. Maybe there are some other controllers, I don't know.
And we are talking about "colored" Macs.
The drive /dev/hda and /dev/hdb is usualy connected to
/pci/*/ata-4/disk{0,1}, so you can search for that.
/dev/hdc and /dev/hdd is connected to ata-3.
If you have a supported Adaptec then you can parse /proc/scsi/aic78xxx
and /proc/scsi/scsi.
I will implement this in my script, the preview on the ftp server works
only with one card right now. I will add the IDE stuff in the next days.
It would be nice to know what I can expect under /proc.
There is a little hardware "detection" script
ftp://ftp.suse.com/pub/suse/ppc/update/BETA/suse_hw_info.sh
Please start it with . ./suse_hw_info.sh and mail us the tar.gz file.
It would be nice to have this for every possible machine, I will make
the infos available to the public.
Gruss Olaf
--
$ man 1 current_release
BUGS
Users never read manuals...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-01 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-01 21:51 find the OF boot-device Olaf Hering
2000-02-01 22:04 ` Olaf Hering
2000-02-01 22:55 ` BenH
2000-02-01 23:23 ` Olaf Hering [this message]
2000-02-03 6:53 ` Takashi Oe
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=20000202002306.A32257@suse.de \
--to=olh@suse.de \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-users@lists.linuxppc.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 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).