headers
David Hinds | 2 Jan 2004 00:12
Favicon

Re: wireless.opts problems

On Mon, Dec 29, 2003 at 01:02:21AM -0500, John H. wrote:
> 
> I understand wireless.opts should be able to automatically do some
> things, like set a wep key, dependent on the essid I am on.
> 
> I have eth1 set to find whatever wireless network is in range,
> and wireless.opts has this as default
> 
> essidany,*,*,*)
>     INFO="Any ESSID"
>     ESSID="any"
>     ;;
> 
> I was wondering, if I could have it to where I do the following, in
> addition to finding any open network 
> 
> if essid="specificid"
> use key="blah"
> 
> thanks.  I want to be able to use both together.  if the specific id
> is matched, and it requires wep(Which it will), use the key. 

In principle you could do this but it doesn't easily fit into the
design of the PCMCIA configuration scripts.  Since they are just shell
scripts, you're free to modify them any way you like for your own use.
But I'm probably not going to add this capability.  The scripts in the
pcmcia-cs package were meant to only provide basic services; now, the
hotplug subsystem is probably a better place to think about adding
more elaborate functionality, since that is meant to be more general
than just for PCMCIA.
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Hinds | 2 Jan 2004 00:20
Favicon

Re: CF memory card vs CF wireless card

On Tue, Dec 23, 2003 at 11:06:50PM -0800, Sriram Neelakandan Iyer wrote:
> 
> I have an ARM7TDMI based chip that has an on board CF controller. I
> have coded the Linux Socket Service Layer based on the SA11xx stuff.
> 
> I am able to read the CIS of a CF memory card properly. dump_cis
> prints the details as per the specs I use a SanDisk 64MB SDCFB card
> and i get the full CIS as per the data sheet properly.
> 
> But when i plugin a CF wireless card, the card detection happens,
> but dump_cis complains "no CIS present" .. i found that the
> Attribute memory was giving out randomly alternating values of 0x00
> & 0xFF.

What does "randomly alternating" mean exactly?

> 1. Is there anything special to be done to handle CF
> Wireless card (i.e. CF+ cards) to read the CIS space ?

All cards should behave the same in regards to reading the CIS; this
is done when the cards are operating in "memory mode" (as opposed to
"memory and IO mode").

> 2. Is there any init sequence to be followed for CF+ card power up ?

It should be the same init sequence that the pcmcia drivers use for
all cards, nothing special.

The only things that jump to mind, are to verify that your socket
driver is setting memory timings correctly.  The pcmcia-core code
(Continue reading)

Permalink | Reply | 3 comments |
headers
Sriram Neelakandan Iyer | 2 Jan 2004 06:54
Picon
Favicon

Re: CF memory card vs CF wireless card

--- David Hinds <dhinds <at> sonic.net> wrote:
> On Tue, Dec 23, 2003 at 11:06:50PM -0800, Sriram
> Neelakandan Iyer wrote:
> > 
> > I have an ARM7TDMI based chip that has an on board
> CF controller. I
> > have coded the Linux Socket Service Layer based on
> the SA11xx stuff.
> > 
> > I am able to read the CIS of a CF memory card
> properly. dump_cis
> > prints the details as per the specs I use a
> SanDisk 64MB SDCFB card
> > and i get the full CIS as per the data sheet
> properly.
> > 
> > But when i plugin a CF wireless card, the card
> detection happens,
> > but dump_cis complains "no CIS present" .. i found
> that the
> > Attribute memory was giving out randomly
> alternating values of 0x00
> > & 0xFF.
> 
> What does "randomly alternating" mean exactly?

ok.. i was wrong in the english usage ..
what i meant was that, some byte locations that are
initially 0x00 become 0xFF in the next read  ( i even
use a JTAG Emulator to read the CIS memory)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Sriram Neelakandan Iyer | 2 Jan 2004 06:55
Picon
Favicon

Re: CF memory card vs CF wireless card

--- David Hinds <dhinds <at> sonic.net> wrote:
> On Tue, Dec 23, 2003 at 11:06:50PM -0800, Sriram
> Neelakandan Iyer wrote:
> > 
> > I have an ARM7TDMI based chip that has an on board
> CF controller. I
> > have coded the Linux Socket Service Layer based on
> the SA11xx stuff.
> > 
> > I am able to read the CIS of a CF memory card
> properly. dump_cis
> > prints the details as per the specs I use a
> SanDisk 64MB SDCFB card
> > and i get the full CIS as per the data sheet
> properly.
> > 
> > But when i plugin a CF wireless card, the card
> detection happens,
> > but dump_cis complains "no CIS present" .. i found
> that the
> > Attribute memory was giving out randomly
> alternating values of 0x00
> > & 0xFF.
> 
> What does "randomly alternating" mean exactly?

ok.. i was wrong in the english usage ..
what i meant was that, some byte locations that are
initially 0x00 become 0xFF in the next read  ( i even
use a JTAG Emulator to read the CIS memory)
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Hinds | 2 Jan 2004 08:08
Favicon

Re: CF memory card vs CF wireless card

On Thu, Jan 01, 2004 at 09:54:00PM -0800, Sriram Neelakandan Iyer wrote:
> > 
> > It should be the same init sequence that the pcmcia
> > drivers use for all cards, nothing special.
> >
> I was asking about the socket drivers layer init
> sequence.

That was what I meant, also.

> > The only things that jump to mind, are to verify
> > that your socket driver is setting memory timings correctly. 
> 
> this is my question too .. Do i need to set different
> memory timings for reading CIS of CF+ card.. ( note
> that with the same timings i am able to read the CIS
> of the SanDisk CF Memory Card ) .. so i suppose the
> timings are correct.

The same timings should be used for all card types.  Some cards might,
however, be more sensitive to whether the timings are correct.

Do both of these cards use the same Vcc, when you test them on the
laptop?  (check with "cardctl status")

-- Dave

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
(Continue reading)

Permalink | Reply | 0 comments |
headers
John H. | 3 Jan 2004 12:06

WPA support for orinoco_cs


Are there plans for WPA support for orinico_cs?

_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Permalink | Reply | 1 comment |
headers
David Hinds | 3 Jan 2004 19:10
Favicon

Re: WPA support for orinoco_cs

On Sat, Jan 03, 2004 at 06:06:55AM -0500, John H. wrote:
> 
> Are there plans for WPA support for orinico_cs?

I am unfamiliar with WPA.  It would probably be better to address your
question to the maintainer of the orinoco driver.

-- Dave

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Permalink | Reply | 0 comments |
headers
Jingmin (Jimmy) Zhou | 6 Jan 2004 10:28

pcmcia with high mem support

Hi,

Recently I've got 2GB (2 x 1GB) RAM for my Dell Latitude C640
laptop. The spec. of the laptop says it officially supports
maximal 1GB (2 x 512MB), however the BIOS successfully
recognizes the 2GB RAM, and WinXP/FreeBSD5.1/Linux2.4/Linux2.6
all can use the 2GB RAM without any problems except that the
orinoco_cs driver does not work any more under Linux. (WinXP/
FreeBSD both can use 2GB RAM and the wireless card without any
problems).

The Laptop has a Dell True Mobile 1150 miniPCI wireless card,
which works fine under Linux 2.4/2.6 with the orinoco_cs driver
before I upgraded the RAM from 256MB to 2GB.

I use pcmcia-cs package (3.2.5 and 3.2.7). Before upgrading
RAM, the cardmgr program could probe and find the wireless card
perfectly. But now, it cannot find the wireless card at all.

Even though I specify the amount of memory to be 256MB as the
boot parameter when I actually have the 2GB installed, the
cardmgr still cannot find the wireless card.

How to solve this problem?

Thanks a lot for help!

Here's part of the dump message of lspci under 2GB Memory:

-------------------- cut below -----------------------------
(Continue reading)

Permalink | Reply | 4 comments |
headers
David Hinds | 6 Jan 2004 18:39
Favicon

Re: pcmcia with high mem support

On Tue, Jan 06, 2004 at 01:28:02AM -0800, Jingmin (Jimmy) Zhou wrote:

> Here's part of the dump message of dmesg under 2GB Memory:
> -------------------- cut below -----------------------------
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>  BIOS-e820: 0000000000100000 - 000000007ffe2800 (usable)
>  BIOS-e820: 000000007ffe2800 - 0000000080000000 (reserved)
>  BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved)
>  BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
> user-defined physical RAM map:
>  user: 0000000000000000 - 000000000009fc00 (usable)
>  user: 000000000009fc00 - 00000000000a0000 (reserved)
>  user: 0000000000100000 - 000000007ffe2800 (usable)

The problem here is the user-specified memory map is bogus.  Note that
this is user-specified.  Or possibly due to a screwed up boot loader.
You are probably using grub?

-- Dave

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Permalink | Reply | 3 comments |
headers
Jingmin (Jimmy) Zhou | 6 Jan 2004 19:58

Re: pcmcia with high mem support

You are correct! I am using grub. So how to solve this problem?
Should I use lilo instead? Thanks!

Jimmy

On Tue, 6 Jan 2004, David Hinds wrote:

> The problem here is the user-specified memory map is bogus.  Note that
> this is user-specified.  Or possibly due to a screwed up boot loader.
> You are probably using grub?
>
> -- Dave

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Permalink | Reply | 2 comments |

Gmane