[EMAIL PROTECTED] (Alan Cox) wrote on 18.11.00 in
<[EMAIL PROTECTED]>:
> > It is. There are plenty of devices for which an arbitrary IN is an
> > irrecoverable state transition.
>
> The ne2000 clones being the most infamous of them. Blind ISA read probing is
> not a safe business
Hell, I've h
> It is. There are plenty of devices for which an arbitrary IN is an
> irrecoverable state transition.
The ne2000 clones being the most infamous of them. Blind ISA read probing is
not a safe business
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
Followup to: <[EMAIL PROTECTED]>
By author:Olivier Galibert <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> What guarantees you that:
> 1- No device will respond 0x for an address it decodes
> 2- No device will crap up on you simply because you've read one
> particular address
>
On Fri, Nov 17, 2000 at 03:27:28PM -0500, Richard B. Johnson wrote:
> Then, you read the port as a WORD (16 bits). If nothing responds,
> you get the value of 0x. If somebody is responding, you will
> read something if it's enabled for writes by devices (reads by the CPU).
What guarantees you
Followup to: <[EMAIL PROTECTED]>
By author:Matthew Kirkwood <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Fri, 17 Nov 2000, Russell King wrote:
>
> > Therefore, it should be reserved independent of whether we have the
> > driver loaded/in kernel or not.
>
> Is this not an argume
On Fri, 17 Nov 2000, Russell King wrote:
> Therefore, it should be reserved independent of whether we have the
> driver loaded/in kernel or not.
Is this not an argument for a more flexible resource allocation
API? One offering both:
res = allocate_resource(restype, dev, RES_ALLOC_UNUSED, re
[EMAIL PROTECTED] ("Richard B. Johnson") writes:
[about PCI setup code]
> This stuff has to be set up before you
> have any resources necessary to execute the output of a 'C' compiler,
> so, if you are looking for 'C' syntax, you are out of luck.
Sorry, but that's plain rubbish.
Some things in
On 17 Nov 2000, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:Russell King <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> >
> > Richard B. Johnson writes:
> > > The code necessary to find the lowest unaliased address looks like
> > > this:
> >
> > Any chance o
On Fri, 17 Nov 2000, Russell King wrote:
> Richard B. Johnson writes:
> > It's Intel assembly on Intel machines. It's a hell of a lot more
> > readable than AT&T assembly. This stuff has to be set up before you
> > have any resources necessary to execute the output of a 'C' compiler,
> > so, if y
Followup to: <[EMAIL PROTECTED]>
By author:Russell King <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Richard B. Johnson writes:
> > The code necessary to find the lowest unaliased address looks like
> > this:
>
> Any chance of providing something more readable? I may be able to re
Richard B. Johnson writes:
> It's Intel assembly on Intel machines. It's a hell of a lot more
> readable than AT&T assembly. This stuff has to be set up before you
> have any resources necessary to execute the output of a 'C' compiler,
> so, if you are looking for 'C' syntax, you are out of luck.
On Fri, 17 Nov 2000, Russell King wrote:
> Richard B. Johnson writes:
> > The code necessary to find the lowest unaliased address looks like
> > this:
>
> Any chance of providing something more readable? I may be able to read
> some x86 asm, but I don't have the time to try to decode that lot.
Richard B. Johnson writes:
> The code necessary to find the lowest unaliased address looks like
> this:
Any chance of providing something more readable? I may be able to read
some x86 asm, but I don't have the time to try to decode that lot.
_
|_| ---
Followup to: <[EMAIL PROTECTED]>
By author:Russell King <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Brian Gerst writes:
> > This is an artifact from the ISA 10-bit IO bus. Many ISA cards do not
> > decode all 16 address bits so you get aliases of the 0x100-0x3ff region
> > through
Followup to: <[EMAIL PROTECTED]>
By author:Russell King <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> I've been looking at a number of VGA cards recently, and I've started
> wondering out the Linux resource management as far as allocation of
> IO ports. I've come to the conclusion
On Fri, 17 Nov 2000, Russell King wrote:
> Richard B. Johnson writes:
> > This can't be.
>
> Richard, before I read any further, I suggest that you get some
> documentation on a few PCI VGA cards and read up on the register
> addresses. You may want to change your assumptions about what can an
> And I can definitely say that if you don't allow access to these "extended"
> VGA ports, BIOSes either enter infinite loops or else terminate without
PCI cards also exist that snoop the ISA bus. Several cards snoop the PCI
transactions that eventually go on to the ISA bus in order to emulate IS
Richard B. Johnson writes:
> This can't be.
Richard, before I read any further, I suggest that you get some
documentation on a few PCI VGA cards and read up on the register
addresses. You may want to change your assumptions about what can and
can't be. ;)
And I can definitely say that if you d
On Fri, 17 Nov 2000, Jeff Garzik wrote:
> Russell King wrote:
> > I've been looking at a number of VGA cards recently, and I've started
> > wondering out the Linux resource management as far as allocation of
> > IO ports. I've come to the conclusion that it does not contain all
> > information n
Jeff Garzik writes:
> Dig through the video card docs, even older ISA video cards let you
> disable I/O decoding on all but a few ports, and/or relocate the ports
> it does use to other areas. Different with every video card, of course,
> but most of them can do this to a greater or lesser extent
Russell King wrote:
> Jeff Garzik writes:
> > If XFree86 not fbdev is using the hardware, you can always have a stub
> > driver that does nothing but reserve the ports. Remember, too, that the
> > ports claimed depend on register settings in the video card and PCI
> > config space..
>
> I wish.
Jeff Garzik writes:
> Russell King wrote:
> > Jeff Garzik writes:
> > > > For example, S3 cards typically use:
> > > >
> > > > 0x0102, 0x42e8, 0x46e8, 0x4ae8, 0x8180 - 0x8200, 0x82e8, 0x86e8,
> > > > 0x8ae8, 0x8ee8, 0x92e8, 0x96e8, 0x9ae8, 0x9ee8, 0xa2e8, 0xa6e8,
> > > > 0xaae8, 0
Russell King wrote:
>
> Brian Gerst writes:
> > This is an artifact from the ISA 10-bit IO bus. Many ISA cards do not
> > decode all 16 address bits so you get aliases of the 0x100-0x3ff region
> > throughout IO space. PCI cards should only use the first 256 ports of
> > any 1k block to avoid a
Brian Gerst writes:
> This is an artifact from the ISA 10-bit IO bus. Many ISA cards do not
> decode all 16 address bits so you get aliases of the 0x100-0x3ff region
> throughout IO space. PCI cards should only use the first 256 ports of
> any 1k block to avoid aliases unless they claim the base
Russell King wrote:
> Jeff Garzik writes:
> > > For example, S3 cards typically use:
> > >
> > > 0x0102, 0x42e8, 0x46e8, 0x4ae8, 0x8180 - 0x8200, 0x82e8, 0x86e8,
> > > 0x8ae8, 0x8ee8, 0x92e8, 0x96e8, 0x9ae8, 0x9ee8, 0xa2e8, 0xa6e8,
> > > 0xaae8, 0xaee8, 0xb2e8, 0xb6e8, 0xbae8,
Russell King wrote:
>
> Hi,
>
> I've been looking at a number of VGA cards recently, and I've started
> wondering out the Linux resource management as far as allocation of
> IO ports. I've come to the conclusion that it does not contain all
> information necessary to allow allocations to be mad
Jeff Garzik writes:
> > For example, S3 cards typically use:
> >
> > 0x0102, 0x42e8, 0x46e8, 0x4ae8, 0x8180 - 0x8200, 0x82e8, 0x86e8,
> > 0x8ae8, 0x8ee8, 0x92e8, 0x96e8, 0x9ae8, 0x9ee8, 0xa2e8, 0xa6e8,
> > 0xaae8, 0xaee8, 0xb2e8, 0xb6e8, 0xbae8, 0xbee8, 0xe2e8,
> > 0xff00 -
Russell King wrote:
> I've been looking at a number of VGA cards recently, and I've started
> wondering out the Linux resource management as far as allocation of
> IO ports. I've come to the conclusion that it does not contain all
> information necessary to allow allocations to be made safely.
>
28 matches
Mail list logo
