Prev: get unicode character OEMTextOut
Next: Direct show Filter
From: Pavel A. on 4 Jun 2005 17:36
For such a device maybe you need an ACPI driver?
( just a wild guess, I never did these )

-PA

"Dean Ramsier" wrote:
> I'm not sure exactly what you mean by ISAPnP support, but I believe the
> hardware and BIOS are ISA PNP capable, and I assume that's been
> implemented in general. However, the GPIO is muxed with a couple of
> other devices (GAME and MIDI) in this Winbond chip, so I (or the BIOS)
> needs to ensure the GPIO is the one that is exposed. How this affects
> PnP, I don't know.
>
> I have some opportunity to have the BIOS modified, as long as it isn't
> too major. But, I need to tell the BIOS guy what needs done, and I'm
> not sure what that should be...
>
> - Dean
>
>
From: Doron Holan [MS] on 4 Jun 2005 13:28
how are you synchronizing access to the GPIO between GAME and MIDI? in the
hardware or do you control the drivers for both of these components? What
it sounds like you want is that the BIOS enumerate a new device w/a unique
HW ID and the hw resources you want to use assigned to it so that you can
load your driver and control the hw.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Dean Ramsier" <dramsier(a)gmail.com> wrote in message
news:1117889534.008569.101420(a)o13g2000cwo.googlegroups.com...
> I'm not sure exactly what you mean by ISAPnP support, but I believe the
> hardware and BIOS are ISA PNP capable, and I assume that's been
> implemented in general. However, the GPIO is muxed with a couple of
> other devices (GAME and MIDI) in this Winbond chip, so I (or the BIOS)
> needs to ensure the GPIO is the one that is exposed. How this affects
> PnP, I don't know.
>
> I have some opportunity to have the BIOS modified, as long as it isn't
> too major. But, I need to tell the BIOS guy what needs done, and I'm
> not sure what that should be...
>
> - Dean
>


From: Dean Ramsier on 5 Jun 2005 18:29
We don't need GAME or MIDI, just GPIO. If the BIOS could make the GPIO
appear as a device, and make it appear somewhere in the IO space that I
can get at easily I'd be happy. However, the BIOS guy (someone from
the board vendor who can make limited, minor changes to the BIOS) is
telling me he doesn't have any way to make the GPIO appear anywhere
else in the address space. I don't know enough about the architecture
to have an opinion on that.

My understanding from reading the chip spec is that the device exposes
it's ISA configuration space area through another IO port range at
0x2E/0x2F. They (WinBond) have defined a mechanism that looks a little
like ISA PNP (without the commands, isolation etc) to get access to
these registers. The GPIO registers are in this area. A previous chip
had a conf register that allowed the GPIO data register (located in
this space) to be mapped somewhere else in IO space. This chip doesn't
have that register, so the BIOS guy is telling me the only way to
control GPIO is to go through the 0x2E/0x2F register pair. Note that
the other two functions (GAME and MIDI) do have config registers that
allow their data regs to be mapped. A pity they decided to leave the
GPIO out this time...

I'm missing some big picture stuff here somewhere. In XP, what is the
mechanism that stops me from just blindly writing the ports at
0x2E/0x2F? It appears that in, say, DOS I can hit these registers
directly, but XP doesn't like it. I can understand that someone else
might already have requested this space, although I don't know who. Is
this area a known system area that the WinBond chip is making use of,
and XP is protecting? In general, is it possible for two different
drivers to get access to the same physical IO space, and if so how? If
I could just get at 0x2E/0x2F I should be ok.

I just stumbled across information in the DDK last night that indicated
I need to use translated IO addresses instead of the known physical
address. I haven't done that (used physical IO addresses directly).
Maybe that is related to my failure to write to these ports?

Thanks for the help!
- Dean

From: Pavel A. on 5 Jun 2005 19:21
"Dean Ramsier" wrote:
...........
> I'm missing some big picture stuff here somewhere. In XP, what is the
> mechanism that stops me from just blindly writing the ports at
> 0x2E/0x2F? It appears that in, say, DOS I can hit these registers
> directly, but XP doesn't like it.

Just break into a kernel debugger right now, and try to r/w these ports.
Does it work?

--PA

From: Dean Ramsier on 6 Jun 2005 13:20
Let's hope not... If I understand correctly, you're talking about an ACPI
function driver. Perusing the docs on this, it seems it would need to be
written in conjunction with an ACPI BIOS, which is probably beyond the scope
of what's possible. Also, it looks to me like an ACPI function driver only
works in "cooked" format, which only allows it to read data?? This being a
GPIO device, I'd need to be able to write it. Doesn't look like that's
supported yet (although I could be completely missing something here...)

- Dean


"Pavel A." <pavel_a(a)NOwritemeNO.com> wrote in message
news:F4EAB3DE-48C4-4F27-8F6C-F5417BD68270(a)microsoft.com...
> For such a device maybe you need an ACPI driver?
> ( just a wild guess, I never did these )
>
> -PA
>
> "Dean Ramsier" wrote:
> > I'm not sure exactly what you mean by ISAPnP support, but I believe the
> > hardware and BIOS are ISA PNP capable, and I assume that's been
> > implemented in general. However, the GPIO is muxed with a couple of
> > other devices (GAME and MIDI) in this Winbond chip, so I (or the BIOS)
> > needs to ensure the GPIO is the one that is exposed. How this affects
> > PnP, I don't know.
> >
> > I have some opportunity to have the BIOS modified, as long as it isn't
> > too major. But, I need to tell the BIOS guy what needs done, and I'm
> > not sure what that should be...
> >
> > - Dean
> >
> >


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: get unicode character OEMTextOut
Next: Direct show Filter