linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "'David Gibson'" <david@gibson.dropbear.id.au>
To: Sanjeev Manral <sanjeevm@sanyo.co.in>
Cc: "'linuxppc-dev@lists.linuxppc.org'" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: pcmcia- config.opts, cis and pci
Date: Thu, 29 Aug 2002 14:21:59 +1000	[thread overview]
Message-ID: <20020829042159.GJ1537@zax> (raw)
In-Reply-To: <6DF87017DA95D611AC6000606730DE9B0BD768@BLREXSR>


On Thu, Aug 29, 2002 at 09:30:27AM +0530, Sanjeev Manral wrote:
>
> Thank you david,
>
> right now I 'm using 16 bit card. does it mean that enabling pci has no
> sigficant as there is no pci bus.

That should be true.

> you can have a look at hardware(visit link)
> http://www.sanyo.com/industrial/semiconductors/systemlsi/IAPr.html
>
> do I need to write a driver for sockets of my controller?

If there isn't a socket driver already available for your PCMCIA
controller hardware, then yes.

> From: David Gibson [mailto:david@gibson.dropbear.id.au]
> Sent: Thursday, August 29, 2002 5:21 AM
> To: 'linuxppc-dev@lists.linuxppc.org'
> Subject: Re: pcmcia- config.opts, cis and pci
>
>
>
> On Wed, Aug 28, 2002 at 03:30:14PM +0530, Sanjeev Manral wrote:
> >
> > Hi all,
> >
> > I'm using pcmcia-cs-3.2.0 my kernel is 2.4.17. It's a ppc405 board.
> >
> > pcmcia-cs is not able to detect ide_cs card and telling it a Blank card.
> >
> > I've tried many options in /etc/pcmcia/config.opts but nothing is working.
> >
> > I'm having one more doubt. there is no PCI brige in manual of my hardware.
> > It is using coreconnect architecture and PCMCIA controller is directly
> > connected to processor local bus. In hardware there is not a single
> mention
> > of pci-plb bridge.
> >
> > If I disable "pci" in "make xconfig" "card bus support" is also disabling
> > and there are no sockets.
> > shall I enable "pci" and "card bus support"( I'm trying this, IS IT
> > CORRECT?)
>
> Probably not - are you using a 16-bit PCMCIA "PC Card" or a 32-bit
> "CardBus" card.  Since you have no PCI, chances are your hardware will
> only support the 16-bit cards.
>
> > I debugged it with enable "pci" and "card bus support". driver is not able
> > to get a valid cis. and trying to load a blank card driver( memory_cs )
> > instead of ide_cs.
> >
> > Is it a problem with only config.opts or some other problem.
> >
> > I don't know where to proceed. if somebody knows how and where to get a
> > valid config.opts please let me know.
> >
> > thanks,
> > Sanjeev
> >
> >
> >
>

--
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

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

  reply	other threads:[~2002-08-29  4:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29  4:00 pcmcia- config.opts, cis and pci Sanjeev Manral
2002-08-29  4:21 ` 'David Gibson' [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-28 10:00 Sanjeev Manral
2002-08-28 23:30 ` Matthew Locke
2002-08-28 23:51 ` David Gibson

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=20020829042159.GJ1537@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sanjeevm@sanyo.co.in \
    /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).