* some booting help
@ 2000-05-12 18:34 David Weis
2000-05-12 18:40 ` David Edelsohn
0 siblings, 1 reply; 4+ messages in thread
From: David Weis @ 2000-05-12 18:34 UTC (permalink / raw)
To: linuxppc-dev
We've started again with the MCA rs/6000's and I needed a bit of help. A
little background on the machine-
It's a rs6000 7011-250 with a 601 PowerPC processor
The io ports on the MCA bus are addressed through a bus unit controller
with a BUID of 0x20. If I wanted to write something to 0x3f8 on the mca
bus, I would have to set up the segment register, etc, correct? Is this
something with enough overhead that I can't realistically do it for every
io port access?
We do have some code by Andrew Richardson that will make a valid boot disk
and print 987 to the display on the front. It's available at
http://www.sjdjweis.com/bboard/q-and-a-fetch-msg.tcl?msg_id=000005&topic_id=1&topic=RS%2f6000%20Linux
Any help is appreciated!
dave
--
David Weis | 10520 New York Ave, Des Moines, IA 50322
djweis@plconline.com | Voice 515-278-0133 Ext 231
| http://www.perfectionlearning.com/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: some booting help
2000-05-12 18:34 some booting help David Weis
@ 2000-05-12 18:40 ` David Edelsohn
2000-05-12 18:50 ` David Weis
0 siblings, 1 reply; 4+ messages in thread
From: David Edelsohn @ 2000-05-12 18:40 UTC (permalink / raw)
To: David Weis; +Cc: linuxppc-dev
I believe that AIX attaches and detaches from the I/O spaces for
every access. It may try to cache values in one or more segment
registers, but not required that it be mapped continually -- if I remember
correctly.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: some booting help
2000-05-12 18:40 ` David Edelsohn
@ 2000-05-12 18:50 ` David Weis
2000-05-12 19:05 ` David Edelsohn
0 siblings, 1 reply; 4+ messages in thread
From: David Weis @ 2000-05-12 18:50 UTC (permalink / raw)
To: David Edelsohn; +Cc: linuxppc-dev
On Fri, 12 May 2000, David Edelsohn wrote:
> I believe that AIX attaches and detaches from the I/O spaces for
> every access. It may try to cache values in one or more segment
> registers, but not required that it be mapped continually -- if I remember
> correctly.
I was looking at the BUSIO_ATT and BUSIO_DET functions in
/usr/include/sys/adspace.h for clues. I had downloaded some AIX driver
source code examples once but can't seem to find them any more.
Thanks
dave
--
David Weis | 10520 New York Ave, Des Moines, IA 50322
djweis@plconline.com | Voice 515-278-0133 Ext 231
| http://www.perfectionlearning.com/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: some booting help
2000-05-12 18:50 ` David Weis
@ 2000-05-12 19:05 ` David Edelsohn
0 siblings, 0 replies; 4+ messages in thread
From: David Edelsohn @ 2000-05-12 19:05 UTC (permalink / raw)
To: David Weis; +Cc: linuxppc-dev
>>>>> David Weis writes:
David> I was looking at the BUSIO_ATT and BUSIO_DET functions in
David> /usr/include/sys/adspace.h for clues. I had downloaded some AIX driver
David> source code examples once but can't seem to find them any more.
See also /usr/include/sys/ioacc.h. AIX device drivers accessing
those types of devices perform a lot of
iocc_val = IOCC_ATT(bus_id, 0);
val = BUSIO_GETC(iocc_val+XXX);
...
BUSIO_PUTC(iocc_val+XXX);
IOCC_DET(iocc_val);
Plus programmed I/O, e.g., pio_assist().
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-05-12 19:05 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-05-12 18:34 some booting help David Weis
2000-05-12 18:40 ` David Edelsohn
2000-05-12 18:50 ` David Weis
2000-05-12 19:05 ` David Edelsohn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).