Hi,
On Tue, 14 Sep 1999, Philip Blundell wrote:
> >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.
> >It's not clear to me yet if Linux is
> >using anything in this area that will conflict with the driver's needs.
> >It looks like the kernels page tables are at 0x4000. Will this cause
> >problems if I try and reserve the memory ranges above for my driver?
>
> 0x600..0x700 is probably OK because that page is pinned down anyway for the
> vector table - though it's usually marked inaccessible to trap NULL
> dereferences. There is no page mapped at 0x1000 per default so you will need
> to create a fixed mapping there if you need it. The page table shouldn't get
> in your way if you stay in the ranges you mentioned?
>
> p.
>
I plan on staying in those ranges, so hopefully it will work to use them
as I have outlined. What is the easiest way to create the mapping, in
head-armv.S, or later on in the initialization? Thanks.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
