From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bitsy questions
Date: Fri, 12 Mar 2004 20:13:29 +0100 [thread overview]
Message-ID: <200403121913.i2CJDTA05825@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Tue, 09 Mar 2004 11:06:28 -0500." <dcf8ad1fb6f3ac2b6925f08914049911@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
I asked:
> > Is the support for pcmcia disks only in the
> > ipaq (bitsy) kernel, or also in the pc one?
and jmk replied:
> there is some disabled code in pc/sdata.c which i put in just to see
> if it would work:
thanks! I have it working now.
took me (quite) some time to find working numbers for port and irq.
I tried guessing them using info from aux/pcmcia, /dev/irqalloc and
/dev/ioalloc, I suppose I'm not smart at this.
Is there a better way?
I choose the first default configuration from aux/pcmcia --
naive question alert :-) just curious:
Are there in general reasons to favor one over the other?
(I attach the output of aux/pcmcia at the end)
Somehow this worked more automatic on the bitsy, I recall.
Is life easier on the bitsy wrt automatic choosing irq's?
Or has more effort (default irq's) been put in for the bitsy?
(I know/think more effort has been put in there wrt the possibility
of sending a configure command to - what was it? - pcm?ctl ?)
Rephrased/Related: just curious: are there intrincic
differences between the bitsy and the pc that make things
easier in one place and harder in another?
For sake of completeness, for my laptop the following
(inserted at the right place in sdata.c) made it work.
I really have no idea how generally useful the irq is.
if(channel == -1) {
isa.port = 0x200; /* toshiba tecra 8000 */
isa.irq = 10; /* toshiba tecra 8000 */
channel = pcmspecial("MK5002MPL", &isa);
}
Axel.
[-- Attachment #2: mk5002mpl --]
[-- Type: text/plain , Size: 1316 bytes --]
device 2048 bytes of 100ns IO+MEM
version 4.1
TOSHIBA
MK5002MPL
configuration registers at (0)0x200 (1)0x202 (2)0x204 (3)0x206
configuration 0 (default)
memory device, Ready/Busy active Memory Wait required
Vcc: Vnominal 5000000uV Iavg 400mA Ipeak 500mA Ipowerdown 60mA
memory address range 0x0 - 0x800
configuration 0
Vcc: Vnominal 3300000uV Ipeak 500mA
configuration 1 (default)
I/O device, Ready/Busy active
Vcc: Vnominal 5000000uV Iavg 400mA Ipeak 500mA Ipowerdown 60mA
IO space 4 address lines selectable 8bit or 8&16bit access
interrupts:level:pulse:shared, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
configuration 1
Vcc: Vnominal 3300000uV Ipeak 500mA
configuration 2 (default)
I/O device, Ready/Busy active
Vcc: Vnominal 5000000uV Iavg 400mA Ipeak 500mA Ipowerdown 60mA
IO space 10 address lines selectable 8bit or 8&16bit access
1f0 - 1f7
3f6 - 3f7
interrupts:level:pulse:shared, 14
configuration 2
Vcc: Vnominal 3300000uV Ipeak 500mA
configuration 3 (default)
I/O device, Ready/Busy active
Vcc: Vnominal 5000000uV Iavg 400mA Ipeak 500mA Ipowerdown 60mA
IO space 10 address lines selectable 8bit or 8&16bit access
170 - 177
376 - 377
interrupts:level:pulse:shared, 14
configuration 3
Vcc: Vnominal 3300000uV Ipeak 500mA
next prev parent reply other threads:[~2004-03-12 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 13:55 [9fans] Plan9 questions and quarrel w0rd 2 th3
2004-03-09 14:11 ` gdiaz
2004-03-09 14:35 ` Fco.J.Ballesteros
2004-03-09 15:08 ` [9fans] Bitsy questions (was: Plan 9 questions and quarrel) Axel Belinfante
2004-03-09 15:39 ` Fco.J.Ballesteros
2004-03-09 16:06 ` jmk
2004-03-12 19:13 ` Axel Belinfante [this message]
2004-03-15 9:38 ` [9fans] Bitsy questions Fco.J.Ballesteros
2004-03-15 9:46 ` Geoff Collyer
2004-03-16 13:21 ` Derek Fawcus
2004-03-16 13:26 ` lucio
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 16:52 [9fans] bitsy questions Fco.J.Ballesteros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200403121913.i2CJDTA05825@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).