1 |
On Saturday 29 January 2011 18:04:07 meino.cramer@×××.de wrote: |
2 |
> Volker Armin Hemmann <volkerarmin@××××××××××.com> [11-01-29 17:56]: |
3 |
> > On Saturday 29 January 2011 17:34:18 meino.cramer@×××.de wrote: |
4 |
> > > Volker Armin Hemmann <volkerarmin@××××××××××.com> [11-01-29 16:39]: |
5 |
> > > > On Saturday 29 January 2011 15:18:10 meino.cramer@×××.de wrote: |
6 |
> > > > > Hi, |
7 |
> > > > > |
8 |
> > > > > when listing my hardware with lshw I find some stuff build |
9 |
> > > > > into my ASUS Crosshair IV Formula, which I seem not to use |
10 |
> > > > > and I like to know, for what it is good for: |
11 |
> > > > > |
12 |
> > > > > These are excerpts from the output of lshw: |
13 |
> > > > > *-serial UNCLAIMED |
14 |
> > > > > |
15 |
> > > > > description: SMBus |
16 |
> > > > > product: SBx00 SMBus Controller |
17 |
> > > > > vendor: ATI Technologies Inc |
18 |
> > > > > physical id: 14 |
19 |
> > > > > bus info: pci@0000:00:14.0 |
20 |
> > > > > version: 41 |
21 |
> > > > > width: 32 bits |
22 |
> > > > > clock: 66MHz |
23 |
> > > > > configuration: latency=0 |
24 |
> > > > |
25 |
> > > > sensors, and spd-eprom are accessed this way. |
26 |
> > > > |
27 |
> > > > > and |
28 |
> > > > > |
29 |
> > > > > *-isa |
30 |
> > > > > |
31 |
> > > > > description: ISA bridge |
32 |
> > > > > product: SB700/SB800 LPC host |
33 |
> > > > > controller |
34 |
> > > > > vendor: ATI Technologies Inc |
35 |
> > > > > physical id: 14.3 |
36 |
> > > > > bus info: pci@0000:00:14.3 |
37 |
> > > > > version: 40 |
38 |
> > > > > width: 32 bits |
39 |
> > > > > clock: 66MHz |
40 |
> > > > > capabilities: isa bus_master |
41 |
> > > > > configuration: latency=0 |
42 |
> > > > |
43 |
> > > > today's incarnation is called 'lpc'. Your sensor chip is |
44 |
> > > > probably |
45 |
> > > > accessed through this. Also connectiopn sensor/superio-chipset. |
46 |
> > > > |
47 |
> > > > > and |
48 |
> > > > > |
49 |
> > > > > *-multimedia |
50 |
> > > > > |
51 |
> > > > > description: Audio device |
52 |
> > > > > product: GF108 High |
53 |
> > > > > Definition Audio |
54 |
> > > > > Controller |
55 |
> > > > > vendor: nVidia Corporation |
56 |
> > > > > physical id: 0.1 |
57 |
> > > > > bus info: pci@0000:08:00.1 |
58 |
> > > > > version: a1 |
59 |
> > > > > width: 32 bits |
60 |
> > > > > clock: 33MHz |
61 |
> > > > > capabilities: pm msi |
62 |
> > > > > pciexpress |
63 |
> > > > > bus_master cap_list |
64 |
> > > > > configuration: driver=HDA |
65 |
> > > > > Intel |
66 |
> > > > > latency=0 |
67 |
> > > > > resources: irq:25 |
68 |
> > > > > memory:fe97c000-fe97ffff |
69 |
> > > > > |
70 |
> > > > > (I have a MSI GT430 (nvidia) card and onboard audio: |
71 |
> > > > > *-multimedia |
72 |
> > > > > |
73 |
> > > > > description: Audio device |
74 |
> > > > > product: SBx00 Azalia (Intel HDA) |
75 |
> > > > > vendor: ATI Technologies Inc |
76 |
> > > > > physical id: 14.2 |
77 |
> > > > > bus info: pci@0000:00:14.2 |
78 |
> > > > > version: 40 |
79 |
> > > > > width: 64 bits |
80 |
> > > > > clock: 33MHz |
81 |
> > > > > capabilities: pm bus_master |
82 |
> > > > > cap_list |
83 |
> > > > > configuration: driver=HDA Intel |
84 |
> > > > > latency=64 |
85 |
> > > > > resources: irq:16 |
86 |
> > > > > memory:fcaf8000-fcafbfff |
87 |
> > > > > |
88 |
> > > > > ). |
89 |
> > > > > |
90 |
> > > > > |
91 |
> > > > > |
92 |
> > > > > lspci -k of those device/chips/whatever does say for the |
93 |
> > > > > nvidia |
94 |
> > > > > audio: |
95 |
> > > > > |
96 |
> > > > > 08:00.1 Audio device: nVidia Corporation GF108 High |
97 |
> > > > > Definition Audio Controller (rev a1) Subsystem: Micro-Star |
98 |
> > > > > International Co., Ltd. Device 2304 |
99 |
> > > > > |
100 |
> > > > > Kernel driver in use: HDA Intel |
101 |
> > > > > Kernel modules: snd-hda-intel |
102 |
> > > > > |
103 |
> > > > > but...for what reason there is an audio device in my |
104 |
> > > > > graphics card? |
105 |
> > > > > Sounds to me like a bicycle with onboard toaster... ;) |
106 |
> > > > |
107 |
> > > > hdmi. |
108 |
> > > > Because hdmi is able to transport sound. Also look up the DRM |
109 |
> > > > mess. |
110 |
> > > > |
111 |
> > > > > for the smbus thingy as for the ISA-bridge there no |
112 |
> > > > > additional info. For what reason there is an ISA bridge on |
113 |
> > > > > a board which skipped floppy controller and IDE??? |
114 |
> > > > |
115 |
> > > > yes. |
116 |
> > > > |
117 |
> > > > > How can I make what use of it? |
118 |
> > > > |
119 |
> > > > you probably already do. |
120 |
> > > |
121 |
> > > How do you define "probably" ? :) |
122 |
> > |
123 |
> > well, your board is able to boot. So the bios is able to access spdrom |
124 |
> > to read the memory settings. This is done via smbus. |
125 |
> > If you use sensors, you are probably using isa/lipc bus to access the |
126 |
> > chip. And even if you don't. Do you have a ps/2 keyboard? The keyboard |
127 |
> > controller sits in the same superio chip as the sensors. |
128 |
> |
129 |
> Ah! I see...but I would think, that the driver for the kbd and/or the |
130 |
> access to the sensors would led to a "Kernel driver in use:"- or |
131 |
> "Kernel modules:"-entry when using lspci -k, where the SMBUS-thingy |
132 |
> is listed. But nothing... |
133 |
> |
134 |
> ? |
135 |
|
136 |
for the kernel the keyboard controller is a different entity ;) |
137 |
the kernel sees the 'old' keyboard driver - a logical equivalent to the old |
138 |
intel 8042. And that is not a pci device. |
139 |
|
140 |
http://en.wikipedia.org/wiki/Keyboard_controller_(computing) |
141 |
http://en.wikipedia.org/wiki/Intel_8042 |