Driver to access the IO mapped hardware

NTDEV
41

OK. Have you looked at the following?

http://smbus.org/specs/smbus_driver_ext_arch10.pdf
http://smbus.org/specs/smbus_cmi10.pdf
http://smbus.org/specs/smbus20.pdf

Good luck,

mm

42

> The problem is that the SMBUS registers are typically already owned by another driver in the system.

Actually, judging from what he is saying here, it looks like this device is in permanently disabled state because there is no matching driver around that can handle it, so that its registers don’t really have an owner. OTOH, how can the application that he received from his customer deal with this device if there is no driver available??? If there is one… well, then the whole thread starting right from the original question seems to be a piece of nonsense. To make things even more ridiculous, WTF would his app need assembly routines if it sends requests to a driver???

The only thing that gets into one head is that the target app is meant to run long before “real” OS even starts loading a kernel(probably it is even 16-bit one)…

Anton Bassov

43

anton bassov wrote:

If there is one… well, then the whole thread starting right from
the original question seems to be a piece of nonsense.

Now you’re getting it :slight_smile:

The only thing that gets into one head is that the target app is
meant to run long before “real” OS even starts loading a kernel
(probably it is even 16-bit one)…

I sort of pictured it more like “Portmon” where all you see is one .exe, but it surreptitiously loads a kernel driver (to do the dirty work) as soon as you run it…

44

> I sort of pictured it more like “Portmon” where all you see is one .exe, but it surreptitiously

loads a kernel driver (to do the dirty work) as soon as you run it…

Again, what is the OP’s role in it if there is already a driver available, and WTF would his customer provide assembly routines to be used in an app???

Anton Bassov

45

Thank you all for your suggestions.

I sort of pictured it more like “Portmon” where all you see is one .exe, but
it surreptitiously
loads a kernel driver (to do the dirty work) as soon as you run it…

Yes its a single .exe

Thanks,
vbkr

46

Well, that cleared THAT up.

Huh??

Peter
OSR

47

Peter Viscarola (OSR) wrote:

Well, that cleared THAT up.

Huh??

Look, about eighty light-years ago, I proposed that this guy’s GUI just invoke the vendor-supplied .exe to tweak the registers or whatever the heck it does. Isn’t that the end goal of this exercise anyway? Just to have a clean GUI for reading/writing registers?

48

Hi Chris,
How to I invoke the vendor .exe to tweak the registers?
Any help appreciated.
Thanks,
vbkr

49

WAIT! You said…

So, you write a program that invokes that.

Isn’t that what we’ve been talking about?

Peter
OSR

50

Hi,
I donot have the source code.
Its the just " exe" which is graphical tool shows the dump of device registers.
I have no idea how you are asking me to invoke it ?
Could you please elaborate on it?

Thanks,
vbkr

51

  1. Have you verified that that program (superbios.exe) can in fact read whatever it is that you think it can? Do the values make any sense?

  2. The thing is, while your particular executable could be absolutely anything, to me, ‘superbios’ refers to a version of AWARD BIOS that went away went Phoenix consumed AWARD a long time ago.

  3. We’ve gone around this many, many, many time, and you simply haven’t anywhere near enough information to complete this task, let alone safely, unless what Peter (and Chris earlier) happens to work.

  4. All they’re saying is that you might be able to simply execute SuperBIOS.exe to perform whatever operations it is that your customer wants, and if you want, you could create a program that handles the actual launching and so forth. This sounds like what you’re customer is asking for - take that program, run it, capture the output to a file or something, parse the output and then display it in some GUI or whatever.

  5. Otherwise, I don’t know what to tell you - you have no documentation for your chipset or anything else. Why your customer won’t give this to you, I have no idea, but I just don’t see how you can possibly proceed.

Good luck,

mm

52

Hi,

Thanks for help.

  1. Have you verified that that program (superbios.exe) can in fact read
    whatever it is that you think it can? Do the values make any sense?

Yes,It shows me all slave device register values.
steps are:
double click the .exe–>select SM bus from the menu –>Select slave device–>Registers displayed
Any way I am looking into this option.

We’ve gone around this many, many, many time, and you simply haven’t
anywhere near enough information to complete this task, let alone safely, unless
what Peter (and Chris earlier) happens to work.

I did find the following document on the web recently and here is the link and this explains pretty much what I was talking about.

http://joostm.nl/solaris/vr/doc/VT8235.pdf

In this document ,if you see
On Page 87(D17:F0),you could see System Management Bus-Specific Configuration Registers
and On page 99,System Management Bus I/O-Space Registers.

My target was to read and write into above registers.

Can you help me giving few more suggestions?

Thanks and best regards,

53

bharat kumar v wrote:

Its the just " exe" which is graphical tool shows the dump of
device registers.
I have no idea how you are asking me to invoke it ?

Oh boy. Well, first of all, I thought “SuperBIOS.exe” was a command-line application, not a GUI. Still,l though, it could work. Launch it in the background, fire some window messages at it to simulate key and button presses, and then read the displayed information off the UI. Look at EnumWindows(), EnumChildWindows(), or whatever.

54

hye kumar;

Do you have an example or reference to achieve it? Appreciated if want to
share.
Tq

On Sat, May 1, 2010 at 11:43 AM, wrote:

> bharat kumar v wrote:
>
> > Its the just " exe" which is graphical tool shows the dump of
> > device registers.
> > I have no idea how you are asking me to invoke it ?
>
> Oh boy. Well, first of all, I thought “SuperBIOS.exe” was a command-line
> application, not a GUI. Still,l though, it could work. Launch it in the
> background, fire some window messages at it to simulate key and button
> presses, and then read the displayed information off the UI. Look at
> EnumWindows(), EnumChildWindows(), or whatever.
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>