Sender: |
|
Date: |
Tue, 25 May 2004 10:55:54 +0200 |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
<40B293C8.27944.505BE788@localhost> |
Content-Type: |
text/plain; charset=US-ASCII; format=flowed |
From: |
|
Parts/Attachments: |
|
|
David Gillett wrote:
>>Memory-addressed cards seems different... infact if, in order to change
>>the state of the MEMCS16, I must decode the SA17-SA23 address, I deduce
>>that my 16 bit memory mapped device can be addressed only between
>>0x03FFFF and FFFFFF... is this right ?
>>
>>
>
> Yes, and no. I think addresses below 0x00FFFF are used for the IVT, and I
>suspect that 0x010000-0x03FFFF may be reserved for other uses, too.
> On the other hand, addresses above 0x0FFFFF are available only from
>protected mode, as the result of decoding through a descriptor. So
>depending on your target software platform, those may be out of bounds as
>well.
>
>David Gillett
>
>
>
Hi David...
I'm still confused... also because I don't know what IVT stay for....
of course... I forgot to tell that I'm working with Linux OS in kernel
space, as I'm writing a kernel driver.
thanks again for your support,
Giampaolo Bellini
PCBUILD's List Owners:
Bob Wright<[log in to unmask]>
Drew Dunn<[log in to unmask]>
|
|
|