Ask for some information about motherboard ASUS NCLV-D

Huang0 at Winbond.com.tw Huang0 at Winbond.com.tw
Wed Apr 13 02:58:10 CEST 2005


Hi Rudolf


> No, this should be activated when you rebuild whole kernel and reboot
the
> machine.
> So you must check via dmesg comamnd or /var/log/something if you can
see that
> line.
> If you just patched and do not build the kernel (make bzImage) than it
cant
> work :)

Yes, I know that, I have rebuilt the kernel before I do the debug and
send
you mail, including the "make bzImage" So the patch should have worked
if it can.


> > Where should I put these "printks"? You'd better give me more
information
> > about it.
> 
> Like in that two routines:
> +static void __init asus_hides_smbus_devices(struct pci_dev *dev) {
> +       if (unlikely(dev->subsystem_vendor == PCI_VENDOR_ID_ASUSTEK))
{
> +                       switch(dev->subsystem_device) {
> +                       case 0x8117: /* ASUS server board (NCLV-D) */
> +                               asus_server_board_hides_smbus_devices
= 1;
> +                      asus_server_board_hides_smbus_devices
> break;
> +                       }
> +       }
> 
> printk("Value of asus_server_board_devices: %d
> \n",asus_server_board_hides_smbus_devices);
> 
> }
> 
> 
> And here:
> 	printk("In INTEL IO REGION QUIRK\n");
>          pci_read_config_dword(dev, 0x58, &region);
>          quirk_io_region(dev, region, 64, PCI_BRIDGE_RESOURCES+1);
> 
> 
> And maybe  here:
> 
> 
> +
val=inb((region&~GPIO_IOSIZE_MASK)+GPIO_OUTPUT2_REG_HIGH);
> 
> printk("oldval: %x\n",val);
> +               val&=~0x4; /* GPIO42 : 0 (Low) */
> +               val|=0x8;  /* GPIO43 : 1 (High) */
> printk("newval: %x\n",val);
> 
> Now I think you will get it. We must find out if our new code is
activated,
> and if not what part failed.

OK, I see, I will continue the debug this afternoon or this night when
my
colleague CFLi is able to share that motherboard.


> > Yes, you are right, I find that the eeprom module works well if I do
NOT
> > do the "isaset" trick. But at this time, the 792 module does NOT
work!
> 
> Yes because it simply switches the bus to some other place. Just
imagine the
> bus as railroad
> and the multiplexer like a "railswitch". So when switched your train
will visit
> different stations,
> but some can remain the same :)

Yes, I know a little about it. My manager LHHsu explained it to me
before,
He also told me: In 792 Windows driver, if we need the 792 information,
we
will switch the multiplexer to enable 792 chip, after we get the
information
from 792, we must switch it back as soon as possible, otherwise some of
the
other parts of the motherboard will be disabled.
I think this is the problem we meet now. :-(
Can we try to use the method in 792 Windows driver for reference?


> > Then do you know how to solve this problem? So that both the eeprom
and
> > 792 modules can work at the same time.
> 
> No I cant Asus did not told us whole true. He messed with more devices
on the
> bus except the monitoring chip.
> When we will have our "quirk" working we can try to experiment or ask
Asus again
> what to do...

Do you mean that the mail I forwarded on 2005-03-09 from ASUS(in HTML
format)
does NOT contain the enough information?
Then need I continue contact ASUS for their help? If you still need
their help,
I think we may continue ask them.

Thanks
Best Regards
Chunhao


===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repea!
 t the  English statement above.¥»«H¥ó¤º©Ò§tµØ¨¹¹q¤lªº°]²£©Ê¾÷±K©Ê¸ê°T, ¶È±ÂÅv­ìµo«H¤H«ü©w¤§¦¬«H¤H¨ú¾\¤§¥Î. °²¨Ï±z¨Ã«D³Q«ü©w¤§¦¬«H¤H©Î¦]¥ô¦ó­ì¦]¦b¥¼¸g±ÂÅvªº±¡§Î¤§¤U¦¬¨ì¥»«H¥ó, ½Ð±z§iª¾­ìµo«H¤H¨Ã¥ß§Y±N«H¥ó±q¹q¸£»Pºô¸ô¦øªA¾¹¤¤¤©¥H®ø°£. ¹ï©ó±zªº¦X§@, §Ú­Ì¥ý¦¹­PÁÂ. ¯S¦¹´£¿ô, ¥ô¦ó¥¼¸g±ÂÅv¾Õ¦Û¨Ï¥ÎµØ¨¹¹q¤lªº¾÷±K¸ê°Tªº¦æ¬°¬O³QÄY®æ¸T¤îªº. «H¥ó»PµØ¨¹¹q¤lÀç·~µLÃö¤§¤º®e,¤£±oµø¬°µØ¨¹¹q¤l¤§¥ß³õ©Î·N¨£.



More information about the lm-sensors mailing list