>> >specific memory needs. In particular, it needs to use memory from 0x600
>> >to 0x700, and 0x1000 to 0x1fff.
>>
>> Er, what for? That sounds like a rather bad idea to me.
>>
>Well, I'm porting a shared memory driver from vxWorks that does TCP/IP
>over the PCI bus, similar to Mark D.'s driver. I would use Mark's, but
>this one requires backwards compatibility with processors running
>vxWorks, so I need to port our driver. I am using Mark's as a
>framework.
Oh, I think I get it now. Those are physical addresses, not virtual ones.
In that case, the thing to do is ignore most of what I wrote before, fiddle
mark_usable_memory_areas so that it keeps the page at 0x1000 reserved for the
kernel, and then just access those pages through the normal kernel mappings at
0xc000xxxx.
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
