Mailinglist Archive: yast-devel (38 mails)

< Previous Next >
Re: [yast-devel] HAL vs hwinfo
  • From: JP Rosevear <jpr@xxxxxxxxxx>
  • Date: Fri, 23 May 2008 18:29:06 +0000
  • Message-id: <1211567347.4385.124.camel@xxxxxxxxxxxxxxxxxxxxx>
On Fri, 2008-05-23 at 10:01 +0200, Michal Zugec wrote:
There was discussion if we can use HAL instead of (or together with)
hwinfo. So first, what is difference between informations that both of
them provides. As an example I'll compare network card:

hwinfo --netcard:

27: PCI 200.0: 0200 Ethernet controller
[Created at pci.301]
UDI: /org/freedesktop/Hal/devices/pci_8086_109a
Unique ID: rBUF.m98l3Qk54R0
Parent ID: z8Q3.ZbAWgKMCoE3
SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Model: "Lenovo ThinkPad T60"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x109a "82573L Gigabit Ethernet Controller"
SubVendor: pci 0x17aa "Lenovo"
SubDevice: pci 0x2001 "ThinkPad T60"
Driver: "e1000"
Driver Modules: "e1000"
Device File: eth0
Memory Range: 0xee000000-0xee01ffff (rw,non-prefetchable)
I/O Ports: 0x3000-0x3fff (rw)
IRQ: 216 (8638 events)
HW Address: 00:16:41:aa:74:56
Link detected: no
Module Alias: "pci:v00008086d0000109Asv000017AAsd00002001bc02sc00i00"
Driver Info #0:
Driver Status: e1000 is active
Driver Activation Cmd: "modprobe e1000"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #12 (PCI bridge)

lshal:

udi = '/org/freedesktop/Hal/devices/pci_8086_109a'
info.bus = 'pci' (string)
info.linux.driver = 'e1000' (string)
info.parent = '/org/freedesktop/Hal/devices/pci_8086_27d0' (string)
info.product = '82573L Gigabit Ethernet Controller' (string)
info.subsystem = 'pci' (string)
info.udi = '/org/freedesktop/Hal/devices/pci_8086_109a' (string)
info.vendor = 'Intel Corporation' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'pci' (string)
linux.sysfs_path =
'/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0' (string)
pci.device_class = 2 (0x2) (int)
pci.device_protocol = 0 (0x0) (int)
pci.device_subclass = 0 (0x0) (int)
pci.linux.sysfs_path =
'/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0' (string)
pci.product = '82573L Gigabit Ethernet Controller' (string)
pci.product_id = 4250 (0x109a) (int)
pci.subsys_product = 'ThinkPad T60' (string)
pci.subsys_product_id = 8193 (0x2001) (int)
pci.subsys_vendor = 'Lenovo' (string)
pci.subsys_vendor_id = 6058 (0x17aa) (int)
pci.vendor = 'Intel Corporation' (string)
pci.vendor_id = 32902 (0x8086) (int)

As you can see some informations are missing in HAL :
- sysfs - driver, link status
- modaliases : available drivers

But maybe we can split hwinfo into HAL and sysfs agent and modaliases
agent, that should work. Steffent, would that works?
Just to know - it's just a research of possibility ;-)

Why can't we just send patches for hal upstream that exposes this info
as hal properties? Or leverage the code in nm-tool which lists the link
status and driver at least.

-JP
--
JP Rosevear <jpr@xxxxxxxxxx>
Novell, Inc.

--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
References