public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Leonardo Pereira Santos <lsantos@pd3•com.br>
To: Linuxppc embedded <linuxppc-embedded@lists•linuxppc.org>
Subject: Card Services in a FADS850SAR board
Date: Tue, 12 Nov 2002 19:26:07 -0200	[thread overview]
Message-ID: <200211121926.09433.lsantos@pd3.com.br> (raw)



	I know, I know, the FADS board is a piece of c**p but it is the only card I
will have for some time now I i stuck with it :( . Ok, I trying to make the
boad's PCMCIA connector work. I'm using a recent kernel (2.4.20-pre11) in a
MPC850 processor, and the PCMCIA card is a WiFi card.
	First I compiled the kernel with built-in PCMCIA support and modules for the
card's drivers. The first strange thing is that the PCMCIA interrupt
generates a sig 11 error (kernel accessed bad area). But if I boot
(initialize Card Services) with the board already connected, the 8xx module
works fine. So I load up the three driver modules I need (hermes, orinoco,
orinoco_cs), but when I do a lsmod, the orinoco_cs is listed as unused.
Shouldn't the cs driver be used by Card Services? In Paul J. Lucas' page
about a PCMCIA in a PowerBook there is a fine "dummies guide" to make it
work. I followed it but CS' cardmanager doesn't load up the drivers, although
it identifies my card. In Paul's page, he says CS versions prior to 3.1.27
don't work out-of-the-box with a powerpc, and the kernel's version is 3.1.22.
	So I went to CS' HP, downloaded and complied  it to my kernel. After starting
CS with a insmod, when I tried to load the socked driver to the 8xx powerpc
(m8xx_pcmcia) , it generates a sig 11 error in the middle of its
initialization. As a desperate measure, I trying to integrate CS' new code
(3.2.3) in the kernel, but that gives me a very strange compilation error in
re resource management code.
	After all this, my questions are:
	Should I tell my boss to give me a new board RIGHT NOW?
	If there is hope of making it work on my card, why the orinoco_cs module is
unused?
	I got the powerpc kernel in bitkeeper, there is another kernel with a more
recent version of CS?
	Am I making something really stupid compiling CS? I justo follow its
Configure script.
	Now the question that I fear: There is need of a ISA bus? If yes, where do I
configure it, as there isn't any option in the general setup menu in the
kernel config.
	I'm configuring my kernel to support:
	- hot plugable devies,
	- CardBus,
	- 8xx support
	The rest is the module support to my WiFi card.
	Sorry for the long mail. I'd be very grateful if anyoune could give me any
information. Thanks a lot!

- --
"All things are ready, if our minds be so"
The Life Of King Henry V - William Sharespeare

Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Pará 330/202
(51) 3337 1237


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-11-12 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 21:26 Leonardo Pereira Santos [this message]
2002-11-12 21:47 ` Card Services in a FADS850SAR board Wolfgang Denk
2002-11-18  4:07 ` Michael Habermann
2002-11-18  5:42   ` ramdisk crash qi zhaoling

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=200211121926.09433.lsantos@pd3.com.br \
    --to=lsantos@pd3$(echo .)com.br \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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