Several "kernel_device" areas.

bridged with qdn.public.bsp
Post Reply
Yuri Skripachov

Several "kernel_device" areas.

Post by Yuri Skripachov » Thu Oct 30, 2003 2:11 pm

Hi, all!

Does anyone know how to touch three different areas in kernel callouts?

I have EPIC, PIC, PCI INTACK areas placed as:

EPIC 0xfdf4xxxx
PIC 0x800000xx
INTACK 0xbffffff0

Can I place such code into init_asinfo:
as_add(0x80000000, 0x87ffffff, AS_ATTR_DEV, "kernel_device", mem);
as_add(0xb8000000, 0xbfffffff, AS_ATTR_DEV, "kernel_device", mem);
as_add(0xf8000000, 0xffffffff, AS_ATTR_DEV, "kernel_device", mem);

Where will these regions be mapped by kernel if this is possible?

Regards,
Yuri Skripachov.

Igor Kovalenko

Re: Several "kernel_device" areas.

Post by Igor Kovalenko » Sun Nov 02, 2003 10:33 pm

I don't know if that is possible, but judging by the fact that kernel_device
is mapped to a fixed address, looks like there is no way.
And I also hear that this hack is going away completely in the next
release...

"Yuri Skripachov" <skripachov@mail.ru> wrote in message
news:bnr56b$2i8$1@inn.qnx.com...
Hi, all!

Does anyone know how to touch three different areas in kernel callouts?

I have EPIC, PIC, PCI INTACK areas placed as:

EPIC 0xfdf4xxxx
PIC 0x800000xx
INTACK 0xbffffff0

Can I place such code into init_asinfo:
as_add(0x80000000, 0x87ffffff, AS_ATTR_DEV, "kernel_device", mem);
as_add(0xb8000000, 0xbfffffff, AS_ATTR_DEV, "kernel_device", mem);
as_add(0xf8000000, 0xffffffff, AS_ATTR_DEV, "kernel_device", mem);

Where will these regions be mapped by kernel if this is possible?

Regards,
Yuri Skripachov.

Yuri Skripachov

Re: Several "kernel_device" areas.

Post by Yuri Skripachov » Mon Nov 03, 2003 5:16 pm

Then kernel should give me a clear way to address to my interrupt controller
and other devices,
shouldn't it?

Now I can do only:

1) disable ints & address translation - touch devices - enable ints. (hello
hello hello how low?)
2) remap EUMB to 0x80100000 (for example) and test bits in PIC (without PCI
INTACK area) (wrong way I think)
3) remap mpc107 to CHRP (i've realised this way) (but any way here is an
address map that differs from board manual :((((((( )

Also I cannot find out a clear docs about register usage in kernel callouts.
Does anyone have this information?

Thanks,

Regards,
Yuri Skripachov.


"Igor Kovalenko" <kovalenko@attbi.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:bo3viq$438$1@inn.qnx.com...
I don't know if that is possible, but judging by the fact that
kernel_device
is mapped to a fixed address, looks like there is no way.
And I also hear that this hack is going away completely in the next
release...

"Yuri Skripachov" <skripachov@mail.ru> wrote in message
news:bnr56b$2i8$1@inn.qnx.com...
Hi, all!

Does anyone know how to touch three different areas in kernel callouts?

I have EPIC, PIC, PCI INTACK areas placed as:

EPIC 0xfdf4xxxx
PIC 0x800000xx
INTACK 0xbffffff0

Can I place such code into init_asinfo:
as_add(0x80000000, 0x87ffffff, AS_ATTR_DEV, "kernel_device",
mem);
as_add(0xb8000000, 0xbfffffff, AS_ATTR_DEV, "kernel_device",
mem);
as_add(0xf8000000, 0xffffffff, AS_ATTR_DEV, "kernel_device",
mem);

Where will these regions be mapped by kernel if this is possible?

Regards,
Yuri Skripachov.



Post Reply

Return to “qdn.public.bsp”