the error disclosure of the config tool is a little bit mystic.
Building the sandpoint configuration says the following:
Creating directory motorola_sandpoint/only
Traceback (most recent call last):
File "motorola_sandpoint/config.py", line 2732, in ?
File "motorola_sandpoint/config.py", line 2649, in writecode
gencode(image.getroot(), file, 1)
File "motorola_sandpoint/config.py", line 2654, in gencode
File "motorola_sandpoint/config.py", line 804, in gencode
file.write("struct device **last_dev_p = &%s.next;\n" %
AttributeError: 'int' object has no attribute 'instance_name'
This looks like an error in the config tool, while it is a mistake in the
config file. Is there any easy way to point the user/developer to the
place in the config file that is wrong (rather than printing a python
traceback)? This could make it a lot easier for newbies to create fresh
linuxbios ports to motherboards whose hardware is basically already
supported and it could safe the regulars quite some time comparing
config files between the ports...
What is the difference between
printk_debug("smbus: %s[%d]->", dev_path(dev->bus->dev),
printk_debug("smbus: %s[%d]->%s", dev_path(dev->bus->dev),
dev->bus->link , dev_path(dev));
the first print
smbus: PCI: 01:01.1->I2C: 50
the second one print
smbus: PCI: 01:01.1-> PCI: 01:01.1
I've just committed changes to the following files used by the VIA Epia
Changes are as follows :-
re-written smbus_read_byte based on intel/i82801dbm after suggestion from ron,
modifications to raminit to handle changes on re-written routine.
This message was sent using ISPMailNow.com
I hope when power is on, my MB can boot without
press the switch. How can I do that?
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.