Quick linux question

[Dave Ashley]

This is off-topic but I'm hoping someone here will know the answer.
In the linux kernel I need to make a module that will map the BOOTROM
of an RTL8139 based network card into PCI memory somewhere. I need to
write the pci config longword at offset 0x30 with the bus address. I can
arbitrarily pick one such as 0xd2000000 and the bootrom appears as expected,
but I don't want to step on anything else that might be using that memory
area. How can I allocate a block of memory in pci address space to know
where to safely map in the bootrom? Also I'll want to free the allocation
on module exit.

Apologies/thanks as the case may be.
-Dave

[Li-Ta Lo]

On Wed, 2004-02-25 at 12:05, Dave Ashley wrote:
> This is off-topic but I'm hoping someone here will know the answer.
> In the linux kernel I need to make a module that will map the BOOTROM
> of an RTL8139 based network card into PCI memory somewhere. I need to
> write the pci config longword at offset 0x30 with the bus address. I can
> arbitrarily pick one such as 0xd2000000 and the bootrom appears as expected,
> but I don't want to step on anything else that might be using that memory
> area. How can I allocate a block of memory in pci address space to know
> where to safely map in the bootrom? Also I'll want to free the allocation
> on module exit.

You probably need ioremap() and iounmap().

Ollie

Canterwood/Springdale

[James Weir]

Can anyone let me know if the documentation for the above chipsets is freely
available/already ported to linuxbios and does the documentation require a
NDA of any kind?

Thanks,

James

Canterwood/Springdale

[ron minnich]

On Thu, 26 Feb 2004, James Weir wrote:
> Can anyone let me know if the documentation for the above chipsets is freely
> available/already ported to linuxbios and does the documentation require a
> NDA of any kind?

Are these new intel chipsets? Intel has changed policy, it seems, and will
no longer release chipset info. I'm not sure how this is going to play
out.

It seems the itanium secrecy policies are percolating down to the rest of 
intel's chipset groups.

ron

Canterwood/Springdale

[James Weir]

Ron,

Yes these are reasonably new Intel Chips, do you know what is the latest
intel chipset which was under the older policy?

James.

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of ron minnich
Sent: 26 February 2004 19:20
To: James Weir
Cc: [e-mail]
Subject: Re: Canterwood/Springdale

On Thu, 26 Feb 2004, James Weir wrote:
> Can anyone let me know if the documentation for the above chipsets is

freely
> available/already ported to linuxbios and does the documentation require a
> NDA of any kind?

Are these new intel chipsets? Intel has changed policy, it seems, and will
no longer release chipset info. I'm not sure how this is going to play
out.

It seems the itanium secrecy policies are percolating down to the rest of 
intel's chipset groups.

ron

_______________________________________________
Linuxbios mailing list
[e-mail]
http://www.clustermatic.org/mailman/listinfo/linuxbios

Canterwood/Springdale

[ron minnich]

On Thu, 26 Feb 2004, James Weir wrote:
> Yes these are reasonably new Intel Chips, do you know what is the latest
> intel chipset which was under the older policy?

e7501

ron

Canterwood/Springdale

[Bari Ari]

ron minnich wrote:
> On Thu, 26 Feb 2004, James Weir wrote:
> > Can anyone let me know if the documentation for the above chipsets is freely
> > available/already ported to linuxbios and does the documentation require a
> > NDA of any kind?
>
> Are these new intel chipsets?

Canterwood=i875
http://developer.intel.com/design/chipsets/875P/

Springdale=i865 and comes in four flavors
http://developer.intel.com/design/chipsets/index.htm?iid=hdnav_dhtml+comp_ch...

-Bari

Canterwood/Springdale

ron minnich  writes:
> On Thu, 26 Feb 2004, James Weir wrote:
> > Can anyone let me know if the documentation for the above chipsets is freely
> > available/already ported to linuxbios and does the documentation require a
> > NDA of any kind?
>
> Are these new intel chipsets? Intel has changed policy, it seems, and will
> no longer release chipset info. I'm not sure how this is going to play
> out.

Well if you have a big enough carrot it looks like it still works...
> It seems the itanium secrecy policies are percolating down to the rest of 
> intel's chipset groups.

At least it is trying.

Eric

[ron minnich]

I think what dave is saying is 'how do I pick a physical address range on 
pci that won't conflict'

there are calls to allocate address maps in the kernel .. what linux
version again?

ron