9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] need to get at 3rd pcmcia slot
@ 2001-09-30  5:07 Steve Kotsopoulos
  2001-09-30  5:35 ` Boyd Roberts
  0 siblings, 1 reply; 3+ messages in thread
From: Steve Kotsopoulos @ 2001-09-30  5:07 UTC (permalink / raw)
  To: 9fans

My ACER-350 laptop has integrated smartcard reader and wavelan,
and the same Megahertz 574B ethernet card in the 1 pcmcia slot
that Boyd recently reported. I'd like to get the wireless ethernet running
but the wavelan isn't recognised as one of the first 2 pcmcia slots.

[btw, why do they make internal devices show up on the pcmcia bus?]

Has anyone modified devi82365.c to support >2 pcmcia slots?

here are the details of what is found, if that helps

term% aux/pcmcia /dev/pcm0attr
device 268435456 bytes of 0ns unknown
attr device 8192 bytes of 150ns EEPROM
version 4.1
        3Com
        Megahertz 574B
        B
        001
configuration registers at (0)0x10000 (1)0x10002
configuration 1 (default)
        I/O device,
        Vcc:  Vnominal 5000000uV Iavg 30mA Ipeak 50mA Ipowerdown 5000uA
        max wait 700ns
        max ready/busy wait 500000ns
        IO space 5 address lines selectable 8bit or 8&16bit access
        interrupts:level, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
term% aux/pcmcia /dev/pcm1attr
device 512 bytes of 100ns IO+MEM
attr device 1536 bytes of 100ns SRAM
version 7.0
        O2Micro
        SmartCardBus Reader
        V1.0
configuration registers at (0)0x220
configuration 1 (default)
        I/O device,
        Vcc:  Vnominal 5000000uV Istatic 13mA Iavg 100mA
        IO space 5 address lines 8bit or 16bit access
        interrupts:level, 3, 4, 5, 7, 9, 10, 11, 12, 13, 15
        memory address range 0x0 - 0x100


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] need to get at 3rd pcmcia slot
  2001-09-30  5:07 [9fans] need to get at 3rd pcmcia slot Steve Kotsopoulos
@ 2001-09-30  5:35 ` Boyd Roberts
  0 siblings, 0 replies; 3+ messages in thread
From: Boyd Roberts @ 2001-09-30  5:35 UTC (permalink / raw)
  To: 9fans

> version 4.1
>         3Com
>         Megahertz 574B
>         B
>         001

yup, that's a 574B.  i'm not going to worry about that, for the
moment.  i'm gonna stick with the 'truckload of magtapes', err
'handful of cd-r's/floppies'.  i'll tame that later.

i want to charm python (and kill configure) first, now i can type.

it's not perfect:

    alt alt-gr ` e

does not give me a �, but i can type that directly.  anyway,
i can type ascii, which is all i need for the moment.

the trouble is that i don't want to make it too vaio specific,
but i don't think it is.  the code changes are trivial, but not
exactly obvious.

writing code on azerty really sucks;  none of the 'special'
characters are easy to get to, it's always alt-gr + char
and the redirection chars show up on scancode 0x56 <sigh>.

and no smashed file-systems :)

and i'm having fun.




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] need to get at 3rd pcmcia slot
@ 2001-09-30 18:37 forsyth
  0 siblings, 0 replies; 3+ messages in thread
From: forsyth @ 2001-09-30 18:37 UTC (permalink / raw)
  To: 9fans

>>[btw, why do they make internal devices show up on the pcmcia bus?]

because that's where they are?
i'm actually happier if they therefore use an existing interface.
the problem on the PC is working out where things are.
PCI looked as though it would solve that (eg, vendor id,device id,port numbers) but
then they added all that IRQ routing stuff.  perhaps next century.



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-09-30 18:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-09-30  5:07 [9fans] need to get at 3rd pcmcia slot Steve Kotsopoulos
2001-09-30  5:35 ` Boyd Roberts
2001-09-30 18:37 forsyth

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).