9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Peter Bosch <pb@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PCMCIA 3CCFE574BT 10/100Mb ethernet driver
Date: Fri, 28 Sep 2001 09:55:41 -0400	[thread overview]
Message-ID: <20010928135547.AA22019A3D@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

For the 575 (CardBus), the PCI BAR2 register contains the address for
the cardbus specific registers.  Treat this address as an array of 3 ulongs
and acknowledge each interrupt as follows:

/* On the 575B and C, interrupts need to be acknowledged in CardBus memory space */
static void
intrack3c575(ulong *cbfns)
{
	cbfns[1] = 0x8000;
}

peter.


[-- Attachment #2: Type: message/rfc822, Size: 2993 bytes --]

From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PCMCIA 3CCFE574BT 10/100Mb ethernet driver
Date: Fri, 28 Sep 2001 08:18:46 -0400
Message-ID: <20010928121849.68177199E7@mail.cse.psu.edu>

I believe, never having seen one, that the 3CCFE574BT is a PCMCIA card based on
the chip used in the 3C905, but without the busmastering capability; the older 3C589
PCMCIA cards were based on the chip used in the original 3C509 series adapters.
The 3CCFE575BT is a Cardbus card using the full capabilities of the 3c905[BC] chips.

I think.

Given the way the 3C589 driver you have initialises and then just uses the base
elnk3 driver, it's possible you could add in the 3CCFE574BT with little change.
Of course, when 3Com wedges these PCI chips into PCMCIA/Cardbus cards there sometimes
are changes in the way they operate, e.g. the way interrupts are acknowledged on
the 3CCFE575BT.

A start would be to run aux/pcmcia and see if it looks plausible; on a 3C589 you get

	% aux/pcmcia
	device 268435456 bytes of 0ns unknown
	attr device 8192 bytes of 150ns EEPROM
	version 4.1
		3Com Corporation
		3C589D
		TP/BNC LAN Card Ver. 2a
		000002
	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 4 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
	configuration 3
		Vcc:  Vnominal 5000000uV Iavg 200mA Ipeak 200mA Ipowerdown 5000uA
	%

Someone here has been working very hard on integrating PCMCIA and Cardbus
support and we can handle the 3CCFE575BT now; there are a lot of changes to make
that happen and it won't be available until the next major release.

--jim

On Fri Sep 28 07:40:32 EDT 2001, boyd@fr.inter.net wrote:
> has anyone got one?  or any pointers?
>
> i'd like, at some point, to have ethernet.
>

             reply	other threads:[~2001-09-28 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 13:55 Peter Bosch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-28 12:18 jmk
2001-09-28 12:34 ` Boyd Roberts
2001-09-28 11:36 Boyd Roberts

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=20010928135547.AA22019A3D@mail.cse.psu.edu \
    --to=pb@research.bell-labs.com \
    --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).