From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200403121913.i2CJDTA05825@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] Bitsy questions In-reply-to: Your message of "Tue, 09 Mar 2004 11:06:28 -0500." References: From: Axel Belinfante Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-2091723110" Date: Fri, 12 Mar 2004 20:13:29 +0100 Topicbox-Message-UUID: 2d1f5a60-eacd-11e9-9e20-41e7f4b1d025 This is a multipart MIME message. --==_Exmh_-2091723110 Content-Type: text/plain; charset=us-ascii 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. --==_Exmh_-2091723110 Content-Type: text/plain ; name="mk5002mpl"; charset=us-ascii Content-Description: mk5002mpl Content-Disposition: attachment; filename="mk5002mpl" 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 --==_Exmh_-2091723110--