From: Roland Riegel <roland.riegel.maillist@gmx.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Fwd: preparing yaboot/ofpath for linux 2.6
Date: Sat, 17 Jan 2004 10:02:10 +0100 [thread overview]
Message-ID: <200401171002.10772.roland.riegel.maillist@gmx.de> (raw)
Hi list!
I posted this to yaboot-devel, but got no answer so far, so I am reposting it
here...
Roland
---------- Weitergeleitete Nachricht ----------
Subject: preparing yaboot/ofpath for linux 2.6
Date: Mittwoch, 14. Januar 2004 16:28
From: Roland Riegel <roland.riegel.maillist@gmx.de>
To: yaboot-devel@lists.penguinppc.org
Hi all!
When upgrading my ibook to kernel 2.6 I noticed that yaboot (that means,
ofpath) does a very bad job in guessing the OF path of the hard disk,
resulting in a hang on next boot.
After having a discussion with Ethan Benson, I checked the current OF
integration in sysfs of linux-2.6.1-rc1-ben1. For some devices, sysfs
contains a file named devspec which describes the OF path. Funnily enough, on
my iBook G4 such a devspec file only exists for the cd/dvd drive, not for the
hard disk:
$ find /sys -name devspec
[...]
/sys/devices/pci0001:01/0001:01:17.0/0.80000000:mac-io/0.00020000:ata-3/devspec
[...]
I do not know why this is the case, probably because they are connected to
different ide interfaces (ata-3/ata-6)?
Ethan agreed that it seems as if OF support is not properly integrated into
sysfs yet. However, for ofpath it is needed that for every ide device (or at
least hard disk) an OF path can be queried. Is it correct that there is no
other way to retrieve this information than to use devspec?
Finally Ethan suggested to bring this issue on-list. So, does anybody have a
solution for this problem?
Greetings,
Roland
-------------------------------------------------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-01-17 9:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200401171002.10772.roland.riegel.maillist@gmx.de \
--to=roland.riegel.maillist@gmx.de \
--cc=linuxppc-dev@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).