On Sun, Feb 10, 2008 at 01:51:18PM -0800, ron minnich wrote:
> This is a possible dts for alix1c. This actually builds and works,
> but linux panics, so that's an issue, but how does it look?
Definately the right direction, but some comments..
> cpus {
> cpupath="0";
> enabled;
> };
> [EMAIL PROTECTED] {
Why both cpus+cpupath and [EMAIL PROTECTED] ?
> [EMAIL PROTECTED] {
> /config/("northbridge/amd/geodelx/apic");
> apicpath="0,0,0";
Why both [EMAIL PROTECTED] and apicpath?
> [EMAIL PROTECTED] {
How come both cpu and domain can be @0 ?
Yes, I know, the meaning of the path depends on the type. Wait, the
containing block type, or the new block type? It is too confusing!
> /config/("northbridge/amd/geodelx/domain");
> enabled;
> [EMAIL PROTECTED] {
What is the pcibus at? Could the number be optional when there is
only one? Rephrase: Is this the PCI bus number? Can we count on it
to always be 0-based and increase by one for each bus?
> [EMAIL PROTECTED],0 {
> /config/("northbridge/amd/geodelx/pci");
> enabled;
> };
What's behind this PCI-PCI-bridge? Is this the external PCI bus?
(By the way, I think we should add a .dts suffix when we have several
files for a component.)
> [EMAIL PROTECTED],0 {
South, on PCI bus 0, south is device 0:f.0. Ok.
> [EMAIL PROTECTED] {
>
> /config/("superio/winbond/w83627hf/dts");
> com1enable = "1";
> };
Now the path is an ioport.
Sorry, I just can't get my head around it. I fear a support problem
too, with the different path types looking very similar but being
quite different.
Which path types do we have so far?
//Peter
--
coreboot mailing list
[email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
