Guys,
I have an Athlon 64-bit host and a Dell P3 500Mhz Target, connected by both a serial and a 1394 cable. I can get Windbg to work fine over the serial, but I cannot get the host to connect to the target over 1394: I get that “Debugee not connected” message, and no matter what I do, it doesn’t budge. Now, the Windbg doc says that I should disable the 1394 Host Controller on the host side, but not the corresponding Network Adapter. Well… on both my Athlon machine and on my Toshiba Laptop, if I disable the 1394 Host Controller the 1394 Network Adapter is also disabled, actually, it disappears totally from the Device Manager list.
Would that be the cause of my problem, or am I barking up the wrong tree ? Tks,
Alberto.
----- Original Message -----
From: S. Drasnin
To: Windows System Software Devs Interest List
Sent: Friday, February 25, 2005 10:15 PM
Subject: Re: [ntdev] SMBUS
hi
The information below that I’m giving you is based on my experience on type of PC.
The SMBus is the bus that is used to interface with the battery. I’ve seen on the web that SMB refers to both the SMBus as well as SMBattery. I don’t know if this is true on all PCs, but Microsoft has a SMBattery driver that talks to the battery through the SMBus. Also, the SMBus is an I2C bus - serial.
Typically, to talk on the SMBus, you go through a special chip that has SMB interface registers. (How you access the registers is covered in the Mindshare book “PCI System Architecture” and probably in the PCI spec. I used I/O port operations when I did it.)
The special chip is a “South Bridge chip”, a chip that resides on the PCI bus, and interfaces to lots of devices (LAN, USB controllers, etc.) and buses (SMB, LPC, etc). The register interfaces are not exactly standard unfortunately – it varies a bit by manufacturer. For example, the Via South Bridge chip has a slightly difference register interface than the ALI South Bridge chip.
One problem with you getting on the SMBus is that you have to worry about other traffic on the bus and deal with collision detection. So, if you were trying to control a device on the SMBus and your system had a battery driver that also talked on the SMBus, you can run into problems.
In the SMBus registers on a South Bridge part, there is a semaphore bit that is used to gain access to the bus - unfortunately it’s not a true semaphore hardware bit – it’s a half-baked attempt at helping to provide sychronization. You can also check another bit, a busy bit, to see if somebody is using the bus. Handling collisions, by backing off for a random amount of time and then trying again, is one way to deal with things as well.
I’m not sure exactly why you choose a PCI board that had an SMBus interface - that info might help us make recommendations.
Sharon
----- Original Message -----
From: Mark Overby
To: Windows System Software Devs Interest List
Sent: Friday, February 25, 2005 9:12 AM
Subject: RE: [ntdev] SMBUS
SMBus can be handled through ACPI (there is a defined way of doing this
in ACPI 3.0 (it was there is previous versions as well)). However, it is
optional and many chipsets have their own drivers or mechanisms for
doing so. There is no “host controller” standard or specification for an
SMBus upper edge interface. (Certainly the SMBus specifications clearly
define what a host shall do on the physical interconnect)
-----Original Message-----
From: xxxxx@listsosr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin Zizka
Sent: Friday, February 25, 2005 3:44 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] SMBUS
Yes, I want to have another interface to the PCI card. It would be a
servicing interface, so I need that driver functional on different types
of chipsets.
So there is no generic SMBus driver? I thought that this is a function
of system bios to handle the SMBus and that this is a standardized
interface to the SMBus. I’ve found a mssmbios.sys installed on different
chipsets, isn’t that a driver that manages the smbus? I havent found any
information about this driver over the internet…
My advantage is that I do not have to support other systems than
windows2000 and windowsXP, because the controlling software does not run
under other systems. So if there would be a support for smbus on that
systems it would be enough for me.
Martin
-----Original Message-----
> From: xxxxx@listsosr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Mats PETERSSON
> Sent: Friday, February 25, 2005 12:10 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] SMBUS
>
>
>
>
>
>
>
> There’s an SMBus driver for Linux out there somewhere.
>
> But essentially, you have to at least configure your driver
> individually for each chipset. The different chipsets are
> probably not dramatically different, but sufficiently that
> you can’t just write an entirely generic driver, you’ll at
> least have to determine which chipset you have and how to
> wiggle the lines around.
>
> What are you trying to achieve? Just a simpler interface to
> your PCI card, or something else?
>
> –
> Mats
>
> -------- Notice --------
> The information in this message is confidential and may be
> legally privileged. It is intended solely for the addressee.
> Access to this message by anyone else is unauthorized. If
> you are not the intended recipient, any disclosure, copying
> or distribution of the message, or any action taken by you in
> reliance on it, is prohibited and may be unlawful. If you
> have received this message in error, please delete it and
> contact the sender immediately. Thank you.
>
>
> xxxxx@lists.osr.com wrote on 02/25/2005 11:02:55 AM:
>
> > Hi everyone.
> >
> > I would like to use a SMBus on my PCI card. I have a
> processor on it
> > that is connected to the system SMBus.
> >
> > My question is - is it possible to create a driver that will be
> > functional on various chipsets without writing a driver for each of
> > it? Do you have an example of this driver? I’ve googled
> some time for
> > any information about SMBus and I haven’t found anything, only that
> > the SMBus is not well supported on Windows and that each
> chipset has
> > its own driver. The only one example that I’ve found (on smbus.org)
> > should enumerate the SMBus devices connected to SMBus, but
> it does not
> > find anything…
> >
> > Martin
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at http://www.
> > osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as:
> xxxxx@3dlabs.com To
> > unsubscribe send a blank email to xxxxx@listsosr.com
>
> > ForwardSourceID:NT0000DB06
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are
> currently subscribed to ntdev as: xxxxx@centrum.cz
> To unsubscribe send a blank email to xxxxx@listsosr.com
>
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@nvidia.com
To unsubscribe send a blank email to xxxxx@listsosr.com
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@listsosr.com
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
