From: mjl <malet.jean-luc@laposte.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: porting sorcerer to udev
Date: Wed, 04 Feb 2004 19:46:01 +0000 [thread overview]
Message-ID: <40214BF9.4070603@laposte.net> (raw)
In-Reply-To: <401633EA.4000102@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
HIPHIP HOURAY
THIS BEGINS TO WOKS!!!!! YEAH!!!! run in happy circle.......
I simply don't understand why this don't worked before.......
let see what i've done :
compile 2.6.2 kernel
create the included patch
and maybe this is the cause : i installed the 2.6.2 headers instead of
2.4.24 one in /usr/include
now what I get :
jlm@Sorcerer:~/devel$ ls /udev/
cdrom hdc mouse0 snd
so this isnt perfect since it miss hda1 and hda2 and the ttys
but this IS a great victory
best regards
note for kyle : as soon as I fix the coldplug issue, sorcerer will be
ready to switch to 2.6 !!!! we are on the right way !!!
[-- Attachment #2: hotplug.patch --]
[-- Type: text/plain, Size: 1198 bytes --]
diff -ru hotplug-2004_01_05/etc/hotplug/pci.rc hotplug-jlm/etc/hotplug/pci.rc
--- hotplug-2004_01_05/etc/hotplug/pci.rc 2003-06-28 02:13:10.000000000 +0200
+++ hotplug-jlm/etc/hotplug/pci.rc 2004-02-04 20:37:52.840130176 +0100
@@ -27,13 +27,9 @@
pci_boot_events ()
{
- #
- # FIXME on 2.5, /sys/bus/pci/devices gives some of this
- # information, and more can be gotten with 'lspci'.
- # don't expect pcimodules to exist!!
- #
- LISTER=`type -p pcimodules`
- if [ "$LISTER" = "" -o ! -f /proc/bus/pci/devices -o ! -x pci.agent ]; then
+
+ LISTER=`type -p lspci`
+ if [ "$LISTER" = "" -o ! -x pci.agent ]; then
echo $"** can't synthesize pci hotplug events"
return
fi
@@ -47,13 +43,11 @@
export ACTION PCI_CLASS PCI_ID PCI_SLOT PCI_SUBSYS_ID
# these notifications will be handled by pcimodules
- for BUS in `cd /proc/bus/pci;find * -type d -print`; do
- for SLOT_FUNC in `cd /proc/bus/pci/$BUS; echo *`; do
- PCI_SLOT=$BUS:$SLOT_FUNC
+ lspci -n | gawk -F ' ' '{printf"%s\n",toupper($4)}' |
+ while read PCI_ID; do
: hotplug pci for $PCI_SLOT
/sbin/hotplug pci
- done
- done
+ done
}
# See how we were called.
next prev parent reply other threads:[~2004-02-04 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 9:48 porting sorcerer to udev MALET JL
2004-01-27 12:43 ` Ananth N Mavinakayanahalli
2004-01-27 16:33 ` Greg KH
2004-01-27 16:35 ` Greg KH
2004-01-27 23:58 ` mjl
2004-01-28 18:56 ` Greg KH
2004-01-28 22:22 ` mjl
2004-01-29 10:00 ` MALET JL
2004-01-30 9:41 ` MALET JL
2004-01-31 23:38 ` mjl
2004-02-02 22:52 ` mjl
2004-02-02 23:09 ` Greg KH
2004-02-03 9:10 ` MALET JL
2004-02-04 19:46 ` mjl [this message]
2004-02-04 20:20 ` mjl
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=40214BF9.4070603@laposte.net \
--to=malet.jean-luc@laposte.net \
--cc=linux-hotplug@vger.kernel.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).