From: Matt_Domsch@Dell.com
To: mochel@osdl.org, greg@kroah.com
Cc: phillips@arcor.de, linux-kernel@vger.kernel.org
Subject: RE: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Wed, 11 Sep 2002 14:09:32 -0500 [thread overview]
Message-ID: <20BF5713E14D5B48AA289F72BD372D68C1E7FF@AUSXMPC122.aus.amer.dell.com> (raw)
> The next logical extension would be to make a symlink 'disk' in each
> directory that points at the PCI
> bus:dev.fn/scsiX/a:b:c:d:disk file for the
> appropriate disk. However, I'm in a quandry... There's no
> simple way to do this.
Or is there? :-)
Patrick, in drivers/base/core.c, there's this concept of platform_notify()
and platform_notify_remove(). Could I exploit this to get callbacks to the
EDD code to create a symlink at that point? These aren't exported to
modules ATM, and I could see how multiple things may want to use this hook -
so instead, how about notifier lists (ala reboot notifiers) that the EDD
code could register with, instead of a single entry? As a list, modules
could add/remove themselves easily.
Then, one more request - giving back the ability to make a symlink given the
device, not just a name.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer, Architect
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next reply other threads:[~2002-09-11 19:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 19:09 Matt_Domsch [this message]
2002-09-12 18:00 ` [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Patrick Mochel
2002-09-12 18:48 ` Matt Domsch
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 3:37 Matt_Domsch
2002-09-30 4:32 Matt_Domsch
[not found] <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com>
2002-09-27 21:30 ` Matt Domsch
2002-09-27 22:33 ` Greg KH
2002-09-29 16:11 ` Dave Jones
2002-09-29 16:18 ` Zwane Mwaikambo
2002-09-29 16:44 ` Alan Cox
2002-09-29 18:20 ` Kai Germaschewski
2002-09-29 18:27 ` Russell King
2002-09-29 18:52 ` Dave Jones
2002-10-01 1:55 ` Patrick Mochel
2002-09-10 22:43 Matt_Domsch
2002-09-09 1:17 Matt_Domsch
2002-09-04 0:54 Matt_Domsch
2002-09-04 1:09 ` Daniel Phillips
2002-09-04 4:17 ` Greg KH
2002-09-08 0:39 ` Patrick Mochel
2002-09-03 22:05 Matt Domsch
2002-09-03 23:29 ` Daniel Phillips
2002-09-04 4:35 ` Andre Hedrick
2002-09-04 16:02 ` Matt Domsch
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=20BF5713E14D5B48AA289F72BD372D68C1E7FF@AUSXMPC122.aus.amer.dell.com \
--to=matt_domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=phillips@arcor.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;
as well as URLs for NNTP newsgroup(s).