From microsoftlottery2007 at microsoft.com  Fri Feb  2 21:50:17 2007
From: microsoftlottery2007 at microsoft.com (MICROSOFT LOTTERY)
Date: Sat, 3 Feb 2007 00:50:17 -0200
Subject: FROM: THE DESK OF THE E-MAIL PROMOTIONS/PRIZE AWARD 
Message-ID: <200702030250.l132oHMf008762@web.foz.net>

FROM: THE DESK OF THE E-MAIL PROMOTIONS MANAGER,
INTERNATIONAL PROMOTIONS/PRIZE AWARD DEPARTMENT
MICROSOFT WORD LOTTERY,UK
61-70 Southampton Row, Bloomsbury,
LONDON, United Kingdom, WC1B 4AR
DIRECTOR:MR. KENT ANDERSON.


REF NO: MSW-L/200-26937
BATCH: 2005MJL-01  

ELECTRONIC MAIL AWARD WINNING NOTIFICATION


!!!CONGRATULATIONS!! !!TO!! !!YOU!!!!!!

 
We are pleased to inform you of the announcement today of winners of the MSW MEGA JACKPOT LOTTO WINNINGS PROGRAMS held on 01st DECEMBER 2006.Your company or your personal e-mail address, is attached to winning number 20-12DEC-2004-02MSW, with serial number S/N-00168 drew the lucky numbers 887-13-865-37-10-83, and consequently won in the first lottery category.


 You have therefore been approved for a lump sum pay out of GBP5,500,000.00 POUNDS in cash which is approximately $10.4 MILLION US DOLLARS credited to file REF NO: MSW-L/200-26937. This is from total prize money of GBP 27,500,000.00 POUNDS, shared among the Twenty (5)international winners in this category.


 All participants were selected through our microsoft computer ballot system drawn form 21,000 names,3,000 names from each continent, as part of International "E-MAIL" Promotions Program, which is conducted annually for our prominent MS WORD user all over the world, and for the 
continues use of E-mail. 

We are sorry to let you know that our site is still under construction, as we are updating our site.Your fund has been deposited in an escrow account and insured with your REF NO: MSW-L/200-26937 and your E-mail address, Please note that, you are to contact us via email and not phone as we are promoting the use of E-mail, any communications with this office should be by mail, You have the right to call the bank, as we will provide you with the necessary details on how to claim your prize. You are to keep your ref, number and batch number from the public, until you have been processed and your money remitted to your account.


 This is part of our security protocol to avoid double claiming and the act of scamming people of their ref number and prizes. We hope with a part of your prize, you will participate in our year high stakes US$1.3 billion International Lottery.


 To claim your winning prize, you must first contact the claims department by email for processing and remittance of your prize money to you. The claims officer contact email is:


CLAIMS OFFICER :MR,JEFF DICKSON.

E-m at il: jeff_dickson12 at hotmail.co.uk OR claimsofficer_2007 at yahoo.co.uk

TELEPHONE# : +44-704-570-2409.



** WINNERS must claim their winning prize before the 28th of march, 2007. All funds not claimed on or before the fixed date will be penalised accordingly.


THIS SHOULD BE COMPLETED BY THE BENEFICIARY OF THE STATED FUND, FOR VERIFICATION BEFORE TRANSFER.
 

BENEFICIARY FIRST NAME-------------
BENEFICIARY LAST NAME--------------
RESIDENTIAL ADDRESS----------------
DATE AND PLACE OF BIRTH------------
TEL. NUMBER------------------------
FAX NUMBER-------------------------
EMAIL ADDRESS----------------------
NEXT OF KIN NAME AND ADDRESS-------
AMOUNT WON-------------------------
BATCH NUMBER-----------------------
REFERENCE N?-----------------------
OCCUPATION-------------------------
MARITAL STATUS----------------------


NOTE: In order to avoid unnecessary delays and complications, please remember to quote your  reference and batch numbers in all correspondences with your claims officer. Do not reply any  other mails like this on net as they are alot of scam artist out there pretending to be us. You may see mails like this do not reply. Do contact your claims officer MR:JEFF DICKSON, at once by email. You will be asked to provide some details to enable us proceed file keeping.

Congratulations!!  Oncemore.

Yours Faithfully,
MRS. PATRICIA LAWRENCE.
LOTTERY CO-ORDINATOR/ANNOUNCER.

NOTE: YOU ARE STRONGLY ADVISED TO KEEP ALL YOUR WINNING CONFIDENTIAL TILL CLAIM IS MADE TO AVOID WRONG CLAIMING.ANY BREACH OF CONFIDENCIAL DISQULIFIES YOU FROM GETTING YOUR PRIZE.     


NOTE: Do not reply this mail. You are to contact your claims officer immediately.

SPONSORS:-
CHIEF SPONSOR;
MICROSOFT COPERATIONS UK;MICROSOFT COPERATIONS ASIA; MICROSOFT COPERATIONS USA ;AMTRAK COURIER EXPRESS;GLOBAL COURIER EXPRESS.


? copyright 2007 by Microsoft Co-operations United Kingdom. All Rights Reserved.





From cga2000 at optonline.net  Sun Feb  4 14:00:31 2007
From: cga2000 at optonline.net (cga2000)
Date: Sun, 04 Feb 2007 14:00:31 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
Message-ID: <20070204190031.GI14439@turki.gavron.org>

I have an old laptop with a 3Com nic/modem combo PC card that works
fine with 2.4 kernels.

$ cardctl ident

Socket 0:
  product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
  manfid: 0x0101, 0x0556
  function: 0 (multifunction)

Recent distros that I have tried to install and a few live CD's are
unable to detect the presence of an ethernet card on this laptop 
even after I load the 3c564_cs module manually.

Since I have tried at least a dozen of the above and keep running into
the same problem, my guess is that support for this model has been
dropped from pcmcia with recent 2.6 kernels. 

Is anyone aware of a workaround for this problem -- even if it means
buying a different pc card -- or does this mean that I need to purchase
a new laptop with a regular PCI NIC..?

I have googled for possible solutions to this problem for over a year
and have not found anything useful so far.

Thanks,

cga




From larry.finger at lwfinger.net  Sun Feb  4 16:20:33 2007
From: larry.finger at lwfinger.net (Larry Finger)
Date: Sun, 04 Feb 2007 15:20:33 -0600
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070204190031.GI14439@turki.gavron.org>
References: <20070204190031.GI14439@turki.gavron.org>
Message-ID: <45C64E21.2010507@lwfinger.net>

cga2000 wrote:
> I have an old laptop with a 3Com nic/modem combo PC card that works
> fine with 2.4 kernels.
> 
> $ cardctl ident
> 
> Socket 0:
>   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
>   manfid: 0x0101, 0x0556
>   function: 0 (multifunction)
> 
> Recent distros that I have tried to install and a few live CD's are
> unable to detect the presence of an ethernet card on this laptop 
> even after I load the 3c564_cs module manually.
> 
> Since I have tried at least a dozen of the above and keep running into
> the same problem, my guess is that support for this model has been
> dropped from pcmcia with recent 2.6 kernels. 
> 
> Is anyone aware of a workaround for this problem -- even if it means
> buying a different pc card -- or does this mean that I need to purchase
> a new laptop with a regular PCI NIC..?

I cannot help you with your current 3Com card; however, I do have a solution that is a lot cheaper
than a new laptop. Roughly one year ago, I needed to upgrade a 10 Mbs PCMCIA card to 100 Mbs. After
some research on suitable cards with Linux drivers, I settled on the Uniden PCN300 card, which sells
for $20 - 25. It uses the in-kernel 8139too driver and has worked just fine for me.

Larry



From matthew at wil.cx  Sun Feb  4 17:04:48 2007
From: matthew at wil.cx (Matthew Wilcox)
Date: Sun, 4 Feb 2007 15:04:48 -0700
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070204190031.GI14439@turki.gavron.org>
References: <20070204190031.GI14439@turki.gavron.org>
Message-ID: <20070204220448.GZ7585@parisc-linux.org>

On Sun, Feb 04, 2007 at 02:00:31PM -0500, cga2000 wrote:
> I have an old laptop with a 3Com nic/modem combo PC card that works
> fine with 2.4 kernels.
> 
> $ cardctl ident
> 
> Socket 0:
>   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
>   manfid: 0x0101, 0x0556
>   function: 0 (multifunction)

This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
$ grep -l 556 drivers/net/3c*
drivers/net/3c59x.c

Have you tried the 3c59x driver?



From cga2000 at optonline.net  Sun Feb  4 17:49:28 2007
From: cga2000 at optonline.net (cga2000)
Date: Sun, 04 Feb 2007 17:49:28 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <45C64E21.2010507@lwfinger.net>
References: <20070204190031.GI14439@turki.gavron.org>
	<45C64E21.2010507@lwfinger.net>
Message-ID: <20070204224928.GL14439@turki.gavron.org>

On Sun, Feb 04, 2007 at 04:20:33PM EST, Larry Finger wrote:
> cga2000 wrote:
> > I have an old laptop with a 3Com nic/modem combo PC card that works
> > fine with 2.4 kernels.
> > 
> > $ cardctl ident
> > 
> > Socket 0:
> >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> >   manfid: 0x0101, 0x0556
> >   function: 0 (multifunction)
> > 
> > Recent distros that I have tried to install and a few live CD's are
> > unable to detect the presence of an ethernet card on this laptop 
> > even after I load the 3c564_cs module manually.
> > 
> > Since I have tried at least a dozen of the above and keep running into
> > the same problem, my guess is that support for this model has been
> > dropped from pcmcia with recent 2.6 kernels. 
> > 
> > Is anyone aware of a workaround for this problem -- even if it means
> > buying a different pc card -- or does this mean that I need to purchase
> > a new laptop with a regular PCI NIC..?

> I cannot help you with your current 3Com card; however, I do have a
> solution that is a lot cheaper than a new laptop. Roughly one year
> ago, I needed to upgrade a 10 Mbs PCMCIA card to 100 Mbs. After some
> research on suitable cards with Linux drivers, I settled on the Uniden
> PCN300 card, which sells for $20 - 25. It uses the in-kernel 8139too
> driver and has worked just fine for me.

Hmm.. what kernel are you running..?  I do have another PCMCIA nic from
Netgear .. if I can locate it  .. 16 bit I think .. and I could give
that a try.

The problem I have with switching back and forth just for a quick test
is that this a cable-modem setup and my ISP check the nic's mac address
to make sure you are legit .. so if you switch to a different nic you
have to call them and say you bought a new computer or something ..
otherwise they won't let you through ..

Thanks,

cga


From cga2000 at optonline.net  Sun Feb  4 17:55:33 2007
From: cga2000 at optonline.net (cga2000)
Date: Sun, 04 Feb 2007 17:55:33 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070204220448.GZ7585@parisc-linux.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
Message-ID: <20070204225533.GM14439@turki.gavron.org>

On Sun, Feb 04, 2007 at 05:04:48PM EST, Matthew Wilcox wrote:
> On Sun, Feb 04, 2007 at 02:00:31PM -0500, cga2000 wrote:
> > I have an old laptop with a 3Com nic/modem combo PC card that works
> > fine with 2.4 kernels.
> > 
> > $ cardctl ident
> > 
> > Socket 0:
> >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> >   manfid: 0x0101, 0x0556
> >   function: 0 (multifunction)
> 
> This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
> $ grep -l 556 drivers/net/3c*
> drivers/net/3c59x.c

Why the "556" ..?

> Have you tried the 3c59x driver?

I'm pretty sure it's CardBus and 32-bit.  But then why would it be any
different with a 2.6 kernel..?  Works fine with 2.27 .. 

I did try the 3c59x driver when installing (.. trying to install..)
debian "etch" .. no joy either.

Thanks,

Chris.





From buytenh at wantstofly.org  Sun Feb  4 19:04:08 2007
From: buytenh at wantstofly.org (Lennert Buytenhek)
Date: Mon, 5 Feb 2007 01:04:08 +0100
Subject: [PATCH 0/2][RFC] pcmcia support for the cirrus logic ep93xx SoC
Message-ID: <20070205000408.GC10978@xi.wantstofly.org>

(please CC, not subscribed to the list)

Hi!

This patch series adds pcmcia support for the cirrus logic ep93xx
SoC.  I've tested it on two different ep93xx boards, and it seems to
work all right.  The first patch in the series adds the generic ep93xx
bits, and the second patch implements the relevant hooks for the ADS
Sphere (ep93xx-based) board.

Comments?


thanks,
Lennert


From buytenh at wantstofly.org  Sun Feb  4 19:05:07 2007
From: buytenh at wantstofly.org (Lennert Buytenhek)
Date: Mon, 5 Feb 2007 01:05:07 +0100
Subject: [PATCH 1/2][RFC] ep93xx pcmcia support
Message-ID: <20070205000507.GD10978@xi.wantstofly.org>

Signed-off-by: Lennert Buytenhek <buytenh at wantstofly.org>

Index: linux-2.6.20/drivers/pcmcia/Kconfig
===================================================================
--- linux-2.6.20.orig/drivers/pcmcia/Kconfig
+++ linux-2.6.20/drivers/pcmcia/Kconfig
@@ -197,6 +197,12 @@ config PCMCIA_AU1X00
 	tristate "Au1x00 pcmcia support"
 	depends on SOC_AU1X00 && PCMCIA
 
+config PCMCIA_EP93XX
+	tristate "EP93xx support"
+	depends on ARM && ARCH_EP93XX && PCMCIA
+	help
+	  Say Y here to include support for the EP93xx PCMCIA controller
+
 config PCMCIA_SA1100
 	tristate "SA1100 support"
 	depends on ARM && ARCH_SA1100 && PCMCIA
Index: linux-2.6.20/drivers/pcmcia/Makefile
===================================================================
--- linux-2.6.20.orig/drivers/pcmcia/Makefile
+++ linux-2.6.20/drivers/pcmcia/Makefile
@@ -27,6 +27,7 @@ obj-$(CONFIG_I82092)				+= i82092.o
 obj-$(CONFIG_TCIC)				+= tcic.o
 obj-$(CONFIG_PCMCIA_M8XX)			+= m8xx_pcmcia.o
 obj-$(CONFIG_HD64465_PCMCIA)			+= hd64465_ss.o
+obj-$(CONFIG_PCMCIA_EP93XX)			+= ep93xx_core.o ep93xx_cs.o
 obj-$(CONFIG_PCMCIA_SA1100)			+= sa11xx_core.o sa1100_cs.o
 obj-$(CONFIG_PCMCIA_SA1111)			+= sa11xx_core.o sa1111_cs.o
 obj-$(CONFIG_PCMCIA_PXA2XX)                     += pxa2xx_core.o pxa2xx_cs.o
@@ -38,6 +39,7 @@ obj-$(CONFIG_PCMCIA_VRC4173)			+= vrc417
 obj-$(CONFIG_OMAP_CF)				+= omap_cf.o
 obj-$(CONFIG_AT91_CF)				+= at91_cf.o
 
+ep93xx_core-y					+= soc_common.o ep93xx_base.o
 sa11xx_core-y					+= soc_common.o sa11xx_base.o
 pxa2xx_core-y					+= soc_common.o pxa2xx_base.o
 
Index: linux-2.6.20/drivers/pcmcia/ep93xx_base.c
===================================================================
--- /dev/null
+++ linux-2.6.20/drivers/pcmcia/ep93xx_base.c
@@ -0,0 +1,194 @@
+/*======================================================================
+
+  Device driver for the PCMCIA control functionality of EP93xx
+  microprocessors.  Derived from pxa2xx_base.c
+
+    The contents of this file may be used under the
+    terms of the GNU Public License version 2 (the "GPL")
+
+    (c) Ian Molton (spyro at f2s.com) 2003
+    (c) Stefan Eletzhofer (stefan.eletzhofer at inquant.de) 2003,4
+    (c) Robert Whaley (rwhaley at applieddata.net) 2005
+
+    derived from sa11xx_base.c
+
+     Portions created by John G. Dorsey are
+     Copyright (C) 1999 John G. Dorsey.
+
+  ======================================================================*/
+
+#include <linux/module.h>
+#include <linux/init.h>
+#include <linux/ioport.h>
+#include <linux/kernel.h>
+#include <linux/spinlock.h>
+#include <linux/platform_device.h>
+#include <linux/dma-mapping.h>
+#include <asm/hardware.h>
+#include <asm/io.h>
+#include <asm/irq.h>
+#include <asm/system.h>
+#include <pcmcia/cs_types.h>
+#include <pcmcia/ss.h>
+#include <pcmcia/bulkmem.h>
+#include <pcmcia/cistpl.h>
+#include "cs_internal.h"
+#include "soc_common.h"
+
+#define PC1ATTRIB		(EP93XX_PCMCIA_CONTROLLER_BASE + 0x20)
+#define PC1COMMON		(EP93XX_PCMCIA_CONTROLLER_BASE + 0x24)
+#define PC1IO			(EP93XX_PCMCIA_CONTROLLER_BASE + 0x28)
+#define PC16BITSWIDE		0x80000000
+
+#define MIN(a,b)		((a) > (b) ? (b) : (a))
+
+#define MCXX_SETUP_MAX		0xff
+#define MCXX_ASST_MAX		0xff
+#define MCXX_HOLD_MAX		0x0f
+
+#define MCXX_SETUP_SHIFT	0
+#define MCXX_ASST_SHIFT		16
+#define MCXX_HOLD_SHIFT		8
+
+
+static inline u_int ep93xx_mcxx_hold(u_int pcmcia_cycle_ns,
+				     u_int hclk_10khz)
+{
+	u_int code = pcmcia_cycle_ns * hclk_10khz;
+	return (code / 100000) + ((code % 100000) ? 1 : 0) - 1;
+}
+
+static inline u_int ep93xx_mcxx_asst(u_int pcmcia_cycle_ns,
+				     u_int hclk_10khz)
+{
+	u_int code = pcmcia_cycle_ns * hclk_10khz;
+	return (code / 100000) + ((code % 100000) ? 1 : 0) - 1;
+}
+
+static inline u_int ep93xx_mcxx_setup(u_int pcmcia_cycle_ns,
+				      u_int hclk_10khz)
+{
+	u_int code = pcmcia_cycle_ns * hclk_10khz;
+	return (code / 100000) + ((code % 100000) ? 1 : 0) - 1;
+}
+
+static int ep93xx_pcmcia_set_mcmem( int sock, int speed, int clock )
+{
+        writel(PC16BITSWIDE
+	     | (MIN(ep93xx_mcxx_setup(speed, clock), MCXX_SETUP_MAX) << MCXX_SETUP_SHIFT)
+	     | (MIN(ep93xx_mcxx_asst(speed, clock), MCXX_ASST_MAX) << MCXX_ASST_SHIFT)
+	     | (MIN(ep93xx_mcxx_hold(speed, clock), MCXX_HOLD_MAX) << MCXX_HOLD_SHIFT),
+	     PC1COMMON);
+
+	return 0;
+}
+
+static int ep93xx_pcmcia_set_mcio( int sock, int speed, int clock )
+{
+        writel(PC16BITSWIDE
+	     | (MIN(ep93xx_mcxx_setup(speed, clock), MCXX_SETUP_MAX) << MCXX_SETUP_SHIFT)
+	     | (MIN(ep93xx_mcxx_asst(speed, clock), MCXX_ASST_MAX) << MCXX_ASST_SHIFT)
+	     | (MIN(ep93xx_mcxx_hold(speed, clock), MCXX_HOLD_MAX) << MCXX_HOLD_SHIFT),
+	     PC1IO);
+
+	return 0;
+}
+
+static int ep93xx_pcmcia_set_mcatt( int sock, int speed, int clock )
+{
+        writel(PC16BITSWIDE
+	     | (MIN(ep93xx_mcxx_setup(speed, clock), MCXX_SETUP_MAX) << MCXX_SETUP_SHIFT)
+	     | (MIN(ep93xx_mcxx_asst(speed, clock), MCXX_ASST_MAX) << MCXX_ASST_SHIFT)
+	     | (MIN(ep93xx_mcxx_hold(speed, clock), MCXX_HOLD_MAX) << MCXX_HOLD_SHIFT),
+	     PC1ATTRIB);
+
+	return 0;
+}
+
+static int ep93xx_pcmcia_set_mcxx(struct soc_pcmcia_socket *skt, unsigned int clk)
+{
+	struct soc_pcmcia_timing timing;
+	int sock = skt->nr;
+
+	soc_common_pcmcia_get_timing(skt, &timing);
+
+	ep93xx_pcmcia_set_mcmem(sock, timing.mem, clk);
+	ep93xx_pcmcia_set_mcatt(sock, timing.attr, clk);
+	ep93xx_pcmcia_set_mcio(sock, timing.io, clk);
+
+	return 0;
+}
+
+static int ep93xx_pcmcia_set_timing(struct soc_pcmcia_socket *skt)
+{
+	unsigned int hclk;
+
+	/* for now just hard code hclk to 100Mhz (in 10khz units)*/
+	hclk = 10000;
+
+	return ep93xx_pcmcia_set_mcxx(skt, hclk);
+}
+
+
+static int ep93xx_drv_pcmcia_probe(struct platform_device *pdev)
+{
+	int ret;
+	struct pcmcia_low_level *ops;
+	int first, nr;
+
+	if (pdev->dev.platform_data == NULL)
+		return -ENODEV;
+
+	ops = (struct pcmcia_low_level *)pdev->dev.platform_data;
+	first = ops->first;
+	nr = ops->nr;
+
+	/* Provide our EP93xx specific timing routines. */
+	ops->set_timing  = ep93xx_pcmcia_set_timing;
+
+	ret = soc_common_drv_pcmcia_probe(&pdev->dev, ops, first, nr);
+
+	return ret;
+}
+
+static int ep93xx_drv_pcmcia_remove(struct platform_device *pdev)
+{
+	return soc_common_drv_pcmcia_remove(&pdev->dev);
+}
+
+static int ep93xx_drv_pcmcia_suspend(struct platform_device *pdev, pm_message_t state)
+{
+	return pcmcia_socket_dev_suspend(&pdev->dev, state);
+}
+
+static int ep93xx_drv_pcmcia_resume(struct platform_device *pdev)
+{
+	return pcmcia_socket_dev_resume(&pdev->dev);
+}
+
+static struct platform_driver ep93xx_pcmcia_driver = {
+	.probe		= ep93xx_drv_pcmcia_probe,
+	.remove		= ep93xx_drv_pcmcia_remove,
+	.suspend 	= ep93xx_drv_pcmcia_suspend,
+	.resume 	= ep93xx_drv_pcmcia_resume,
+	.driver		= {
+		.name	= "ep93xx-pcmcia",
+	},
+};
+
+static int __init ep93xx_pcmcia_init(void)
+{
+	return platform_driver_register(&ep93xx_pcmcia_driver);
+}
+
+static void __exit ep93xx_pcmcia_exit(void)
+{
+	platform_driver_unregister(&ep93xx_pcmcia_driver);
+}
+
+fs_initcall(ep93xx_pcmcia_init);
+module_exit(ep93xx_pcmcia_exit);
+
+MODULE_AUTHOR("Robert Whaley <rwhaley at applieddata.net>");
+MODULE_DESCRIPTION("Linux PCMCIA Card Services: EP93xx core socket driver");
+MODULE_LICENSE("GPL");
Index: linux-2.6.20/drivers/pcmcia/soc_common.c
===================================================================
--- linux-2.6.20.orig/drivers/pcmcia/soc_common.c
+++ linux-2.6.20/drivers/pcmcia/soc_common.c
@@ -49,6 +49,9 @@
 #include "soc_common.h"
 
 /* FIXME: platform dependent resource declaration has to move out of this file */
+#ifdef CONFIG_ARCH_EP93XX
+#include <asm/arch/pcmcia.h>
+#endif
 #ifdef CONFIG_ARCH_PXA
 #include <asm/arch/pxa-regs.h>
 #endif
Index: linux-2.6.20/include/asm-arm/arch-ep93xx/pcmcia.h
===================================================================
--- /dev/null
+++ linux-2.6.20/include/asm-arm/arch-ep93xx/pcmcia.h
@@ -0,0 +1,19 @@
+/*
+ * linux/include/asm-arm/arch-ep93xx/pcmcia.h
+ */
+
+#ifndef __ASM_ARCH_PCMCIA_H
+#define __ASM_ARCH_PCMCIA_H
+
+#define _PCMCIA(slt)		(0x40000000 + ((slt) ? 0x10000000 : 0))
+#define _PCMCIAIO(slt)		_PCMCIA(slt)
+#define _PCMCIAAttr(slt)	(_PCMCIA(slt) + 0x08000000)
+#define _PCMCIAMem(slt)		(_PCMCIA(slt) + 0x0c000000)
+
+#define PCMCIASp		0x10000000
+#define PCMCIAIOSp		0x04000000
+#define PCMCIAAttrSp		0x04000000
+#define PCMCIAMemSp		0x04000000
+
+
+#endif


From buytenh at wantstofly.org  Sun Feb  4 19:05:39 2007
From: buytenh at wantstofly.org (Lennert Buytenhek)
Date: Mon, 5 Feb 2007 01:05:39 +0100
Subject: [PATCH 2/2][RFC] ep93xx pcmcia support for the ads sphere board
Message-ID: <20070205000539.GE10978@xi.wantstofly.org>

Signed-off-by: Lennert Buytenhek <buytenh at wantstofly.org>

Index: linux-2.6.19/drivers/pcmcia/Makefile
===================================================================
--- linux-2.6.19.orig/drivers/pcmcia/Makefile
+++ linux-2.6.19/drivers/pcmcia/Makefile
@@ -55,6 +55,8 @@ au1x00_ss-$(CONFIG_MIPS_DB1500)			+= au1
 au1x00_ss-$(CONFIG_MIPS_DB1550)			+= au1000_db1x00.o
 au1x00_ss-$(CONFIG_MIPS_XXS1500)		+= au1000_xxs1500.o
 
+ep93xx_cs-$(CONFIG_MACH_ADSSPHERE)		+= ep93xx_adssphere.o
+
 sa1111_cs-y					+= sa1111_generic.o
 sa1111_cs-$(CONFIG_ASSABET_NEPONSET)		+= sa1100_neponset.o
 sa1111_cs-$(CONFIG_SA1100_BADGE4)		+= sa1100_badge4.o
Index: linux-2.6.19/drivers/pcmcia/ep93xx_adssphere.c
===================================================================
--- /dev/null
+++ linux-2.6.19/drivers/pcmcia/ep93xx_adssphere.c
@@ -0,0 +1,167 @@
+/*
+ * linux/drivers/pcmcia/ep93xx_adssphere.c
+ * Copyright (C) 2005 Robert Whaley <rwhaley at applieddata.net>
+ *
+ * Adapted from pxa27x_mainstone.c, which is:
+ *   Copyright (C) 2004 MontaVista Software Inc.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ */
+
+#include <linux/module.h>
+#include <linux/init.h>
+#include <linux/kernel.h>
+#include <linux/errno.h>
+#include <linux/interrupt.h>
+#include <linux/device.h>
+#include <linux/platform_device.h>
+#include <pcmcia/ss.h>
+#include <asm/io.h>
+#include <asm/hardware.h>
+#include <asm/irq.h>
+#include <asm/mach-types.h>
+#include <asm/arch/gpio.h>
+#include <asm/arch/adssphere.h>
+#include "soc_common.h"
+
+#define EP93XX_GPIO_PFDR	EP93XX_GPIO_REG(0x30)
+
+#define PCMCIACNT		(EP93XX_PCMCIA_CONTROLLER_BASE + 0x40)
+
+
+static struct pcmcia_irqs irqs[] = {
+	{ 0, IRQ_EP93XX_GPIO(EP93XX_GPIO_LINE_MCCD1),  "PCMCIA CD1" },
+	{ 0, IRQ_EP93XX_GPIO(EP93XX_GPIO_LINE_MCCD2),  "PCMCIA CD2" },
+	{ 0, IRQ_EP93XX_GPIO(EP93XX_GPIO_LINE_MCBVD1), "PCMCIA STSCHG/BVD1" },
+	{ 0, IRQ_EP93XX_GPIO(EP93XX_GPIO_LINE_MCBVD2), "PCMCIA SPKR/BVD2" },
+};
+
+static int adssphere_pcmcia_hw_init(struct soc_pcmcia_socket *skt)
+{
+	if (skt->nr == 0) {
+		skt->irq = IRQ_EP93XX_GPIO(EP93XX_GPIO_LINE_READY);
+		return soc_pcmcia_request_irqs(skt, irqs, ARRAY_SIZE(irqs));
+	}
+
+	return -ENXIO;
+}
+
+static void adssphere_pcmcia_hw_shutdown(struct soc_pcmcia_socket *skt)
+{
+	soc_pcmcia_free_irqs(skt, irqs, ARRAY_SIZE(irqs));
+}
+
+static void adssphere_pcmcia_socket_state(struct soc_pcmcia_socket *skt,
+					  struct pcmcia_state *state)
+{
+	unsigned long status;
+
+	status = readl(EP93XX_GPIO_PFDR);
+	state->detect = (status & 0x06) ? 0 : 1;
+	state->ready  = (status & 0x40) ? 1 : 0;
+	state->wrprot = (status & 0x01) ? 0 : 1;
+	state->bvd1   = (status & 0x08) ? 1 : 0;
+	state->bvd2   = (status & 0x10) ? 1 : 0;
+	state->vs_3v  = (status & 0x20) ? 0 : 1;
+	state->vs_Xv  = (status & 0x80) ? 0 : 1;
+}
+
+static int adssphere_pcmcia_configure_socket(struct soc_pcmcia_socket *skt,
+					     const socket_state_t *state)
+{
+	unsigned long clrbits;
+	unsigned long setbits;
+
+	if (skt->nr != 0) {
+		printk(KERN_ERR "%s: socket %u invalid\n", __func__, skt->nr);
+		return -1;
+	}
+
+	clrbits = 0;
+	setbits = 0;
+
+	switch (state->Vcc) {
+	case 0:
+		clrbits = ADSSPHERE_CR0_CF_33 | ADSSPHERE_CR0_CF_50;
+		setbits = 0;
+		break;
+
+	case 33:
+		clrbits = ADSSPHERE_CR0_CF_50;
+		setbits = ADSSPHERE_CR0_CF_33;
+		break;
+
+	case 50:
+		clrbits = ADSSPHERE_CR0_CF_33;
+		setbits = ADSSPHERE_CR0_CF_50;
+		break;
+
+	default:
+		printk(KERN_ERR "%s: bad Vcc %u\n", __func__, state->Vcc);
+		return -1;
+	}
+
+	writel((readl(ADSSPHERE_CR0) & ~clrbits) | setbits, ADSSPHERE_CR0);
+
+	if (state->flags & SS_RESET)
+		/* see EP93xx User's Guide */
+		writel(0x15, PCMCIACNT);
+	else
+		/* CF mode -  BIT1 for PCMCIA mode */
+		writel(0x11, PCMCIACNT);
+
+	return 0;
+}
+
+static void adssphere_pcmcia_socket_init(struct soc_pcmcia_socket *skt)
+{
+	soc_pcmcia_enable_irqs(skt, irqs, ARRAY_SIZE(irqs));
+}
+
+static void adssphere_pcmcia_socket_suspend(struct soc_pcmcia_socket *skt)
+{
+	soc_pcmcia_disable_irqs(skt, irqs, ARRAY_SIZE(irqs));
+}
+
+static struct pcmcia_low_level adssphere_pcmcia_ops = {
+	.owner			= THIS_MODULE,
+	.hw_init		= adssphere_pcmcia_hw_init,
+	.hw_shutdown		= adssphere_pcmcia_hw_shutdown,
+	.socket_state		= adssphere_pcmcia_socket_state,
+	.configure_socket	= adssphere_pcmcia_configure_socket,
+	.socket_init		= adssphere_pcmcia_socket_init,
+	.socket_suspend		= adssphere_pcmcia_socket_suspend,
+	.nr			= 1,
+};
+
+static struct platform_device adssphere_pcmcia = {
+	.name		= "ep93xx-pcmcia",
+	.id		= -1,
+	.dev		= {
+		.platform_data	= &adssphere_pcmcia_ops,
+	},
+};
+
+static int __init adssphere_pcmcia_init(void)
+{
+	int ret;
+
+	ret = 0;
+	if (machine_is_adssphere())
+		ret = platform_device_register(&adssphere_pcmcia);
+
+	return ret;
+}
+
+static void __exit adssphere_pcmcia_exit(void)
+{
+	if (machine_is_adssphere())
+		platform_device_unregister(&adssphere_pcmcia);
+}
+
+module_init(adssphere_pcmcia_init);
+module_exit(adssphere_pcmcia_exit);
+
+MODULE_LICENSE("GPL");
Index: linux-2.6.19/include/asm-arm/arch-ep93xx/adssphere.h
===================================================================
--- linux-2.6.19.orig/include/asm-arm/arch-ep93xx/adssphere.h
+++ linux-2.6.19/include/asm-arm/arch-ep93xx/adssphere.h
@@ -8,6 +8,8 @@
 
 #define ADSSPHERE_CPLD_REG(x)		(ADSSPHERE_CPLD_VIRT_BASE + (x))
 #define ADSSPHERE_CR0			ADSSPHERE_CPLD_REG(0x00)
+ #define ADSSPHERE_CR0_CF_33		0x01
+ #define ADSSPHERE_CR0_CF_50		0x02
 #define ADSSPHERE_CR1			ADSSPHERE_CPLD_REG(0x04)
  #define ADSSPHERE_CR1_CODEC_POWER	0x20
  #define ADSSPHERE_CR1_AMP_POWER	0x10


From matthew at wil.cx  Sun Feb  4 21:30:24 2007
From: matthew at wil.cx (Matthew Wilcox)
Date: Sun, 4 Feb 2007 19:30:24 -0700
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070204225533.GM14439@turki.gavron.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
Message-ID: <20070205023024.GA7585@parisc-linux.org>

On Sun, Feb 04, 2007 at 05:55:33PM -0500, cga2000 wrote:
> On Sun, Feb 04, 2007 at 05:04:48PM EST, Matthew Wilcox wrote:
> > On Sun, Feb 04, 2007 at 02:00:31PM -0500, cga2000 wrote:
> > > $ cardctl ident
> > > 
> > > Socket 0:
> > >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> > >   manfid: 0x0101, 0x0556
> > >   function: 0 (multifunction)
> > 
> > This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
> > $ grep -l 556 drivers/net/3c*
> > drivers/net/3c59x.c
> 
> Why the "556" ..?

Two reasons, one is the product info: 3CCFEM556
and the other is the manfid: 0x0556

> > Have you tried the 3c59x driver?
> 
> I'm pretty sure it's CardBus and 32-bit.  But then why would it be any
> different with a 2.6 kernel..?  Works fine with 2.27 .. 

Possibly there's a PCI ID missing from the 3c59x driver.  What does
lspci tell you about the card?  Do you have yenta_socket loaded so you
can see the card in the slot?


From cga2000 at optonline.net  Sun Feb  4 22:15:36 2007
From: cga2000 at optonline.net (cga2000)
Date: Sun, 04 Feb 2007 22:15:36 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070205023024.GA7585@parisc-linux.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
Message-ID: <20070205031536.GB22698@turki.gavron.org>

On Sun, Feb 04, 2007 at 09:30:24PM EST, Matthew Wilcox wrote:
> On Sun, Feb 04, 2007 at 05:55:33PM -0500, cga2000 wrote:
> > On Sun, Feb 04, 2007 at 05:04:48PM EST, Matthew Wilcox wrote:
> > > On Sun, Feb 04, 2007 at 02:00:31PM -0500, cga2000 wrote:
> > > > $ cardctl ident
> > > > 
> > > > Socket 0:
> > > >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> > > >   manfid: 0x0101, 0x0556
> > > >   function: 0 (multifunction)
> > > 
> > > This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
> > > $ grep -l 556 drivers/net/3c*
> > > drivers/net/3c59x.c
> > 
> > Why the "556" ..?
> 
> Two reasons, one is the product info: 3CCFEM556
> and the other is the manfid: 0x0556

With 2.4 kernels the 3c574_cs driver is in drivers/net/pcmcia/

Nothing in this directory contains the "556" string

> > > Have you tried the 3c59x driver?
> > 
> > I'm pretty sure it's CardBus and 32-bit.  But then why would it be any
> > different with a 2.6 kernel..?  Works fine with 2.27 .. 
> 
> Possibly there's a PCI ID missing from the 3c59x driver.  What does
> lspci tell you about the card?  Do you have yenta_socket loaded so you
> can see the card in the slot?

With the 2.4 kernel, I definetely do have yenta_socket loaded.

OTOH, lspci does not see the card.  Only sees the cardbus device. 

To display info about the PC cards I need to use cardctl.

With a recent 2.6 kernel, I have to give it another shot -- ie. run
another install or better boot a live CD.

But do you mean that with recent 2.6 kernels pcmcia nic's are handled
like any other PCI nic?

Thanks,

cga




From cga2000 at optonline.net  Sun Feb  4 23:06:58 2007
From: cga2000 at optonline.net (cga2000)
Date: Sun, 04 Feb 2007 23:06:58 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070205023024.GA7585@parisc-linux.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
Message-ID: <20070205040658.GB1344@turki.gavron.org>

On Sun, Feb 04, 2007 at 09:30:24PM EST, Matthew Wilcox wrote:
> On Sun, Feb 04, 2007 at 05:55:33PM -0500, cga2000 wrote:
> > On Sun, Feb 04, 2007 at 05:04:48PM EST, Matthew Wilcox wrote:
> > > On Sun, Feb 04, 2007 at 02:00:31PM -0500, cga2000 wrote:
> > > > $ cardctl ident
> > > > 
> > > > Socket 0:
> > > >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> > > >   manfid: 0x0101, 0x0556
> > > >   function: 0 (multifunction)
> > > 
> > > This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
> > > $ grep -l 556 drivers/net/3c*
> > > drivers/net/3c59x.c
> > 
> > Why the "556" ..?
> 
> Two reasons, one is the product info: 3CCFEM556
> and the other is the manfid: 0x0556
> 
> > > Have you tried the 3c59x driver?
> > 
> > I'm pretty sure it's CardBus and 32-bit.  But then why would it be any
> > different with a 2.6 kernel..?  Works fine with 2.27 .. 
> 
> Possibly there's a PCI ID missing from the 3c59x driver.  What does
> lspci tell you about the card?  Do you have yenta_socket loaded so you
> can see the card in the slot?

Update:

rebooted the debian "etch" installer and tried the 3c59x driver but am
still getting the same result..

are you suggesting that I might need a patched version so my modem/nic
combo is recognized?

Thanks,

cga


From bugme-daemon at bugzilla.kernel.org  Mon Feb  5 01:34:47 2007
From: bugme-daemon at bugzilla.kernel.org (bugme-daemon at bugzilla.kernel.org)
Date: Sun, 4 Feb 2007 22:34:47 -0800
Subject: [Bug 7788] System freeze as soon as PCMCIA card is inserted
Message-ID: <200702050634.l156Ylk3031668@fire-2.osdl.org>

http://bugzilla.kernel.org/show_bug.cgi?id=7788





------- Additional Comments From egypt at nmt.edu  2007-02-04 22:25 -------
I have the same problem with a wireless card (senao with prism chipset). 
Immediate system freeze upon insertion, no logs anywhere that I can find. I too
am running Gentoo.

pcmciautils-014-r1
udev-103



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


From bugme-daemon at bugzilla.kernel.org  Mon Feb  5 01:45:42 2007
From: bugme-daemon at bugzilla.kernel.org (bugme-daemon at bugzilla.kernel.org)
Date: Sun, 4 Feb 2007 22:45:42 -0800
Subject: [Bug 7788] System freeze as soon as PCMCIA card is inserted
Message-ID: <200702050645.l156jg97031954@fire-2.osdl.org>

http://bugzilla.kernel.org/show_bug.cgi?id=7788





------- Additional Comments From egypt at nmt.edu  2007-02-04 22:36 -------
Sorry i forgot to add this in my previous post.

When the card is inserted while the machine is off, at boot time the system
hangs at the "Letting udev process events" step.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


From stuge-linux-pcmcia at cdy.org  Mon Feb  5 02:09:40 2007
From: stuge-linux-pcmcia at cdy.org (Peter Stuge)
Date: Mon, 5 Feb 2007 08:09:40 +0100
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070205040658.GB1344@turki.gavron.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
	<20070205040658.GB1344@turki.gavron.org>
Message-ID: <20070205070940.11415.qmail@cdy.org>

On Sun, Feb 04, 2007 at 11:06:58PM -0500, cga2000 wrote:
> > > > >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> > > > 
> > > > This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.

The 3CCFEM556 is a 16-bit PCMCIA card, not a CardBus card.


> > Possibly there's a PCI ID missing from the 3c59x driver.  What
> > does lspci tell you about the card?  Do you have yenta_socket
> > loaded so you can see the card in the slot?
> 
> Update:
> 
> rebooted the debian "etch" installer and tried the 3c59x driver but
> am still getting the same result..

You're definately looking for the 3c574_cs driver in 2.6 kernels.

pcmcia-cs-3.2.8 comes with a .cis and a .dat file for this card, have
you made the information within available to the 2.6 pcmcia drivers?
See http://kernel.org/pub/linux/utils/kernel/pcmcia/howto.html under
"2.5. The difficult cases: CIS overrides"
(Basically copy 3CCFEM556.dat to /lib/firmware/3CCFEM556.cis)


> are you suggesting that I might need a patched version so my modem/nic
> combo is recognized?

I think it should just work.


//Peter


From cga2000 at optonline.net  Mon Feb  5 22:15:37 2007
From: cga2000 at optonline.net (cga2000)
Date: Mon, 05 Feb 2007 22:15:37 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070205070940.11415.qmail@cdy.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
	<20070205040658.GB1344@turki.gavron.org>
	<20070205070940.11415.qmail@cdy.org>
Message-ID: <20070206031537.GG1344@turki.gavron.org>

On Mon, Feb 05, 2007 at 02:09:40AM EST, Peter Stuge wrote:
> On Sun, Feb 04, 2007 at 11:06:58PM -0500, cga2000 wrote:
> > > > > >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> > > > > 
> > > > > This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
> 
> The 3CCFEM556 is a 16-bit PCMCIA card, not a CardBus card.
> 
> 
> > > Possibly there's a PCI ID missing from the 3c59x driver.  What
> > > does lspci tell you about the card?  Do you have yenta_socket
> > > loaded so you can see the card in the slot?
> > 
> > Update:
> > 
> > rebooted the debian "etch" installer and tried the 3c59x driver but
> > am still getting the same result..
> 
> You're definately looking for the 3c574_cs driver in 2.6 kernels.
> 
> pcmcia-cs-3.2.8 comes with a .cis and a .dat file for this card, have
> you made the information within available to the 2.6 pcmcia drivers?
> See http://kernel.org/pub/linux/utils/kernel/pcmcia/howto.html under
> "2.5. The difficult cases: CIS overrides"
> (Basically copy 3CCFEM556.dat to /lib/firmware/3CCFEM556.cis)
> 
> 
> > are you suggesting that I might need a patched version so my modem/nic
> > combo is recognized?
> 
> I think it should just work.

Light at the end of the tunnel?

Thank you very much -- I've been stuck on a debian etch install for over
a year because of this .. and together with  the howto pointer .. this
is just about the first time I feel like I am -- at last .. making some
kind of progress.

I won't have the time to do this tonight but my guess is that before the
network hardware detection step in the install, I should switch to a
shell and check the contents of /lib/firmware and if the relevant "cis"
is not there, I should be able to copy it over from my sarge 2.4.27
system.

If this doesn't work, I could always skip the network steps in the
install and do it after I reboot the newly-installed system.

Just have to check the 2.6 pcmcia howto for the details such as whether
I need to download a more recent version of CCCFEM556.dat/.cis.

Thanks a bunch,

cga




From bunk at stusta.de  Tue Feb  6 17:13:14 2007
From: bunk at stusta.de (Adrian Bunk)
Date: Tue, 6 Feb 2007 23:13:14 +0100
Subject: hostap_cs_{resume,suspend}(): inconsequent NULL checking
Message-ID: <20070206221314.GM27397@stusta.de>

The Coverity checker spotted the following in 
drivers/net/wireless/hostap/hostap_cs.c:

<--  snip  -->

...
static int hostap_cs_suspend(struct pcmcia_device *link)
{
        struct net_device *dev = (struct net_device *) link->priv;
        int dev_open = 0;
        struct hostap_interface *iface = NULL;

        if (dev)
                iface = netdev_priv(dev);

        PDEBUG(DEBUG_EXTRA, "%s: CS_EVENT_PM_SUSPEND\n", dev_info);
        if (iface && iface->local)
                dev_open = iface->local->num_dev_open > 0;
        if (dev_open) {
                netif_stop_queue(dev);
                netif_device_detach(dev);
        }
        prism2_suspend(dev);

        return 0;
}

static int hostap_cs_resume(struct pcmcia_device *link)
{
        struct net_device *dev = (struct net_device *) link->priv;
        int dev_open = 0;
        struct hostap_interface *iface = NULL;

        if (dev)
                iface = netdev_priv(dev);

        PDEBUG(DEBUG_EXTRA, "%s: CS_EVENT_PM_RESUME\n", dev_info);

        if (iface && iface->local)
                dev_open = iface->local->num_dev_open > 0;

        prism2_hw_shutdown(dev, 1);
        prism2_hw_config(dev, dev_open ? 0 : 1);
        if (dev_open) {
                netif_device_attach(dev);
                netif_start_queue(dev);
        }

        return 0;
}
...

<--  snip  -->

The problem is that if the "if (dev)" is false, there's a guaranteed 
NULL dereference later in the "prism2_suspend(dev)" resp.
"prism2_hw_config(dev, dev_open ? 0 : 1)".

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed




From bugme-daemon at bugzilla.kernel.org  Tue Feb  6 17:42:22 2007
From: bugme-daemon at bugzilla.kernel.org (bugme-daemon at bugzilla.kernel.org)
Date: Tue, 6 Feb 2007 14:42:22 -0800
Subject: [Bug 6454] cs socket<n>: Unable to apply power
Message-ID: <200702062242.l16MgM6d010674@fire-2.osdl.org>

http://bugzilla.kernel.org/show_bug.cgi?id=6454

bunk at stusta.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bunk at stusta.de
             Status|NEW                         |REJECTED
         Resolution|                            |INSUFFICIENT_DATA



------- Additional Comments From bunk at stusta.de  2007-02-06 14:33 -------
Please reopen this bug if it is still present with kernel 2.6.20.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


From dlclark at chtech.com  Thu Feb  8 16:08:17 2007
From: dlclark at chtech.com (David Clark)
Date: Thu, 8 Feb 2007 15:08:17 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
Message-ID: <002a01c74bc5$41ff7650$0f01a8c0@longhorn>

I have a custom embedded board with a single PCMCIA slot.  The PCMCIA
socket controller is a TI PCI1620 (Yenta).  The processor is a Freescale
MPC8245 (PowerPC 603e core).  I am running Linux kernel 2.6.14.2 and
pcmciautils 014.

The PCMCIA slot works with a 32-bit network card that I have been using
during development.  It does not work with a 16-bit card.  When I plug
the 16-bit card into the socket I get the message "cs: unable to map
card memory"

I have searched many user groups, including this one, and I have played
with various settings in the config.opts file, to no avail.  Admittedly
I don't have a good understanding of how pcmcia works in Linux so
hopefully someone here can direct me.

Below are the outputs for (dmesg, config.opts, iomem and ioports).
Please let me know if any further information would be helpful.  Thank
you for your help.

David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark at chtech.com



*********** dmesg *****************
dmesg
Linux version 2.6.14.2ch1 (pcadmin at localhost.localdomain) (gcc version
3.4.1 200
40714 (TimeSys 3.4.1-7)) #250 PREEMPT Wed Feb 7 12:23:19 CST 2007
Host bridge in Agent mode
C&H VXI Intelligent Carrier Platform
Port by C&H Technologies, Inc.
On node 0 totalpages: 32768
  DMA zone: 32768 pages, LIFO batch:15
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/ram rw console=ttyVXI
ip=192.168.1.228:::255.255.
255.0:vx411c::off
OpenPIC Version 1.2 (1 CPUs and 11 IRQ sources) at fc040000
PID hash table entries: 1024 (order: 10, 16384 bytes)
time_init: decrementer frequency = 100.000000 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 125440k available (1644k kernel code, 496k data, 100k init, 0k
highmem)
Calibrating delay loop... 199.68 BogoMIPS (lpj=399360)
Mount-cache hash table entries: 512
checking if image is initramfs...it isn't (no cpio magic); looks like an
initrd
Freeing initrd memory: 1856k freed
softlockup thread 0 started up.
NET: Registered protocol family 16
PCI: Probing PCI hardware
PCI: Scanning bus 0000:00
PCI: Found 0000:00:00.0 [1057/0006] 000e00 00
PCI: Calling quirk c000c184 for 0000:00:00.0
PCI: Calling quirk c00c0f6c for 0000:00:00.0
PCI: Calling quirk c00c0dec for 0000:00:00.0
PCI: Found 0000:00:10.0 [12be/3042] 000e00 00
PCI: Calling quirk c000c184 for 0000:00:10.0
PCI: Calling quirk c00c0f6c for 0000:00:10.0
PCI: Calling quirk c00c0dec for 0000:00:10.0
PCI: Found 0000:00:13.0 [104c/ac23] 000604 01
PCI: Calling quirk c000c184 for 0000:00:13.0
PCI: Calling quirk c00c0f6c for 0000:00:13.0
PCI: Calling quirk c00c0dec for 0000:00:13.0
PCI: Found 0000:00:14.0 [104c/ac54] 000607 02
PCI: Calling quirk c000c184 for 0000:00:14.0
PCI: Calling quirk c00c0f6c for 0000:00:14.0
PCI: Calling quirk c00c0dec for 0000:00:14.0
PCI: Found 0000:00:14.2 [104c/8201] 000880 00
PCI: Calling quirk c000c184 for 0000:00:14.2
PCI: Calling quirk c00c0f6c for 0000:00:14.2
PCI: Calling quirk c00c0dec for 0000:00:14.2
PCI: Fixups for bus 0000:00
PCI: Scanning behind PCI bridge 0000:00:13.0, config 010100, pass 0
PCI: Scanning bus 0000:01
PCI: Fixups for bus 0000:01
PCI: Bus scan for 0000:01 returning with max=01
PCI: Scanning behind PCI bridge 0000:00:14.0, config 020200, pass 0
PCI: Scanning behind PCI bridge 0000:00:13.0, config 010100, pass 1
PCI: Scanning behind PCI bridge 0000:00:14.0, config 020200, pass 1
PCI: Bus scan for 0000:00 returning with max=05
PCI: fixup irq: (0000:00:00.0) got 0
PCI: fixup irq: (0000:00:10.0) got 20
PCI: fixup irq: (0000:00:13.0) got 0
PCI: fixup irq: (0000:00:14.0) got 19
PCI: fixup irq: (0000:00:14.2) got 19
PCI: Cannot allocate resource region 1 of device 0000:00:00.0
  got res [80000000:80000fff] bus [80000000:80000fff] flags 200 for BAR
1 of 000
0:00:00.0
PCI: moved device 0000:00:00.0 resource 1 (200) to 80000000
fsl-i2c.1: failed to claim resource 0
unable to register device 0
fsl-dma.0: failed to claim resource 0
unable to register device 1
fsl-dma.1: failed to claim resource 0
unable to register device 2
Registering openpic with sysfs...
Generic PHY: Registered new driver
PCI: Calling quirk c00c0cc0 for 0000:00:00.0
PCI: Calling quirk c00c0cc0 for 0000:00:10.0
PCI: Calling quirk c00c0cc0 for 0000:00:13.0
PCI: Calling quirk c00c0cc0 for 0000:00:14.0
PCI: Calling quirk c00c0cc0 for 0000:00:14.2
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
ttyS0 at MMIO 0xfc004500 (irq = 25) is a 16550A
io scheduler noop registered
io scheduler deadline registered
RAMDISK driver initialized: 4 RAM disks of 32768K size 1024 blocksize
QS6612: Registered new driver
Yenta: CardBus bridge found at 0000:00:14.0 [0000:0000]
PCI: Bus 2, cardbus bridge: 0000:00:14.0
  IO window: 00000000-000001ff
  IO window: 00000400-000005ff
  PREFETCH window: bf8ff000-bfcfefff
  MEM window: 80400000-807fffff
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:14.0, mfunc 0x00101000, devctl 0x66
Yenta TI: socket 0000:00:14.0 probing PCI interrupt failed, trying to
fix
Yenta TI: socket 0000:00:14.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:00:14.0 parallel PCI interrupts ok
Yenta: ISA IRQ mask 0x0000, PCI irq 19
Socket status: 30000410
pcmcia: parent PCI bridge I/O window: 0xfe000000 - 0xfebfffff
pcmcia: parent PCI bridge Memory window: 0x80000000 - 0xfcffffff
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: No network devices available.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 100k init
cs: memory probe 0x80000000-0xfcffffff:<7> - nothing to change...
 - nothing to change...
 excluding 0x80000000-0xfcffffff
cs: unable to map card memory!
cs: unable to map card memory!
 - nothing to change...
 - data bits = 8
 - parity = none
 - stop bits = 1
 - RTS/CTS is disabled
 - baud rate = 57600<7> - data bits = 7
 - parity = none
 - stop bits = 1
 - RTS/CTS is disabled
 - INBOUND XON/XOFF is enabled, XON = 11, XOFF = 13<7> - OUTBOUND
XON/XOFF is en
abled, XON = 11, XOFF = 13<7> - baud rate = 57600<7> - nothing to
change...
 - nothing to change...
 - nothing to change...
 - nothing to change...

*********** /etc/pcmcia/config.opts *****************
include port 0xFE000000-0xFE0001FF
include port 0xFE000400-0xFE0005FF
include memory 0x80400000-0x807FFFFF
include memory 0xBF8FF000-0xBFCFEFFF


*********** iomem *****************
~ # cat /proc/iomem
80000000-fcffffff : PCI host bridge
  80000000-80000fff : 0000:00:00.0
  80400000-807fffff : PCI CardBus #02
  bf8ff000-bfcfefff : PCI CardBus #02
  bfcff000-bfcfffff : 0000:00:14.0
    bfcff000-bfcfffff : yenta_socket
  bfd00000-bfdfffff : PCI Bus #01
  bfe00000-bfefffff : PCI Bus #01
  bfff8000-bfffffff : 0000:00:10.0
  fc004500-fc004507 : serial

*********** ioports *****************
~ # cat /proc/ioports
fe000000-febfffff : PCI host bridge
  fe000000-fe0001ff : PCI CardBus #02
  fe000400-fe0005ff : PCI CardBus #02
  febf9fc0-febf9fff : 0000:00:14.2
  febfe000-febfefff : PCI Bus #01
  febffff8-febfffff : 0000:00:10.0

 






From linux at dominikbrodowski.net  Thu Feb  8 16:11:38 2007
From: linux at dominikbrodowski.net (Dominik Brodowski)
Date: Thu, 8 Feb 2007 16:11:38 -0500
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <002a01c74bc5$41ff7650$0f01a8c0@longhorn>
References: <002a01c74bc5$41ff7650$0f01a8c0@longhorn>
Message-ID: <20070208211138.GA20710@isilmar.linta.de>

Hi,

What's the output of lspcmcia -vvv ?

	Dominik

On Thu, Feb 08, 2007 at 03:08:17PM -0600, David Clark wrote:
> I have a custom embedded board with a single PCMCIA slot.  The PCMCIA
> socket controller is a TI PCI1620 (Yenta).  The processor is a Freescale
> MPC8245 (PowerPC 603e core).  I am running Linux kernel 2.6.14.2 and
> pcmciautils 014.
> 
> The PCMCIA slot works with a 32-bit network card that I have been using
> during development.  It does not work with a 16-bit card.  When I plug
> the 16-bit card into the socket I get the message "cs: unable to map
> card memory"
> 
> I have searched many user groups, including this one, and I have played
> with various settings in the config.opts file, to no avail.  Admittedly
> I don't have a good understanding of how pcmcia works in Linux so
> hopefully someone here can direct me.
> 
> Below are the outputs for (dmesg, config.opts, iomem and ioports).
> Please let me know if any further information would be helpful.  Thank
> you for your help.
> 
> David Clark
> Senior Software Engineer
> C&H Technologies, Inc
> Web: http:\\www.chtech.com
> Phone: 512-733-2621
> Fax: 512-733-2629
> Email: dlclark at chtech.com
> 
> 
> 
> *********** dmesg *****************
> dmesg
> Linux version 2.6.14.2ch1 (pcadmin at localhost.localdomain) (gcc version
> 3.4.1 200
> 40714 (TimeSys 3.4.1-7)) #250 PREEMPT Wed Feb 7 12:23:19 CST 2007
> Host bridge in Agent mode
> C&H VXI Intelligent Carrier Platform
> Port by C&H Technologies, Inc.
> On node 0 totalpages: 32768
>   DMA zone: 32768 pages, LIFO batch:15
>   Normal zone: 0 pages, LIFO batch:1
>   HighMem zone: 0 pages, LIFO batch:1
> Built 1 zonelists
> Kernel command line: root=/dev/ram rw console=ttyVXI
> ip=192.168.1.228:::255.255.
> 255.0:vx411c::off
> OpenPIC Version 1.2 (1 CPUs and 11 IRQ sources) at fc040000
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> time_init: decrementer frequency = 100.000000 MHz
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 125440k available (1644k kernel code, 496k data, 100k init, 0k
> highmem)
> Calibrating delay loop... 199.68 BogoMIPS (lpj=399360)
> Mount-cache hash table entries: 512
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
> Freeing initrd memory: 1856k freed
> softlockup thread 0 started up.
> NET: Registered protocol family 16
> PCI: Probing PCI hardware
> PCI: Scanning bus 0000:00
> PCI: Found 0000:00:00.0 [1057/0006] 000e00 00
> PCI: Calling quirk c000c184 for 0000:00:00.0
> PCI: Calling quirk c00c0f6c for 0000:00:00.0
> PCI: Calling quirk c00c0dec for 0000:00:00.0
> PCI: Found 0000:00:10.0 [12be/3042] 000e00 00
> PCI: Calling quirk c000c184 for 0000:00:10.0
> PCI: Calling quirk c00c0f6c for 0000:00:10.0
> PCI: Calling quirk c00c0dec for 0000:00:10.0
> PCI: Found 0000:00:13.0 [104c/ac23] 000604 01
> PCI: Calling quirk c000c184 for 0000:00:13.0
> PCI: Calling quirk c00c0f6c for 0000:00:13.0
> PCI: Calling quirk c00c0dec for 0000:00:13.0
> PCI: Found 0000:00:14.0 [104c/ac54] 000607 02
> PCI: Calling quirk c000c184 for 0000:00:14.0
> PCI: Calling quirk c00c0f6c for 0000:00:14.0
> PCI: Calling quirk c00c0dec for 0000:00:14.0
> PCI: Found 0000:00:14.2 [104c/8201] 000880 00
> PCI: Calling quirk c000c184 for 0000:00:14.2
> PCI: Calling quirk c00c0f6c for 0000:00:14.2
> PCI: Calling quirk c00c0dec for 0000:00:14.2
> PCI: Fixups for bus 0000:00
> PCI: Scanning behind PCI bridge 0000:00:13.0, config 010100, pass 0
> PCI: Scanning bus 0000:01
> PCI: Fixups for bus 0000:01
> PCI: Bus scan for 0000:01 returning with max=01
> PCI: Scanning behind PCI bridge 0000:00:14.0, config 020200, pass 0
> PCI: Scanning behind PCI bridge 0000:00:13.0, config 010100, pass 1
> PCI: Scanning behind PCI bridge 0000:00:14.0, config 020200, pass 1
> PCI: Bus scan for 0000:00 returning with max=05
> PCI: fixup irq: (0000:00:00.0) got 0
> PCI: fixup irq: (0000:00:10.0) got 20
> PCI: fixup irq: (0000:00:13.0) got 0
> PCI: fixup irq: (0000:00:14.0) got 19
> PCI: fixup irq: (0000:00:14.2) got 19
> PCI: Cannot allocate resource region 1 of device 0000:00:00.0
>   got res [80000000:80000fff] bus [80000000:80000fff] flags 200 for BAR
> 1 of 000
> 0:00:00.0
> PCI: moved device 0000:00:00.0 resource 1 (200) to 80000000
> fsl-i2c.1: failed to claim resource 0
> unable to register device 0
> fsl-dma.0: failed to claim resource 0
> unable to register device 1
> fsl-dma.1: failed to claim resource 0
> unable to register device 2
> Registering openpic with sysfs...
> Generic PHY: Registered new driver
> PCI: Calling quirk c00c0cc0 for 0000:00:00.0
> PCI: Calling quirk c00c0cc0 for 0000:00:10.0
> PCI: Calling quirk c00c0cc0 for 0000:00:13.0
> PCI: Calling quirk c00c0cc0 for 0000:00:14.0
> PCI: Calling quirk c00c0cc0 for 0000:00:14.2
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
> disabled
> ttyS0 at MMIO 0xfc004500 (irq = 25) is a 16550A
> io scheduler noop registered
> io scheduler deadline registered
> RAMDISK driver initialized: 4 RAM disks of 32768K size 1024 blocksize
> QS6612: Registered new driver
> Yenta: CardBus bridge found at 0000:00:14.0 [0000:0000]
> PCI: Bus 2, cardbus bridge: 0000:00:14.0
>   IO window: 00000000-000001ff
>   IO window: 00000400-000005ff
>   PREFETCH window: bf8ff000-bfcfefff
>   MEM window: 80400000-807fffff
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:00:14.0, mfunc 0x00101000, devctl 0x66
> Yenta TI: socket 0000:00:14.0 probing PCI interrupt failed, trying to
> fix
> Yenta TI: socket 0000:00:14.0 falling back to parallel PCI interrupts
> Yenta TI: socket 0000:00:14.0 parallel PCI interrupts ok
> Yenta: ISA IRQ mask 0x0000, PCI irq 19
> Socket status: 30000410
> pcmcia: parent PCI bridge I/O window: 0xfe000000 - 0xfebfffff
> pcmcia: parent PCI bridge Memory window: 0x80000000 - 0xfcffffff
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 3, 32768 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> IP-Config: No network devices available.
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 100k init
> cs: memory probe 0x80000000-0xfcffffff:<7> - nothing to change...
>  - nothing to change...
>  excluding 0x80000000-0xfcffffff
> cs: unable to map card memory!
> cs: unable to map card memory!
>  - nothing to change...
>  - data bits = 8
>  - parity = none
>  - stop bits = 1
>  - RTS/CTS is disabled
>  - baud rate = 57600<7> - data bits = 7
>  - parity = none
>  - stop bits = 1
>  - RTS/CTS is disabled
>  - INBOUND XON/XOFF is enabled, XON = 11, XOFF = 13<7> - OUTBOUND
> XON/XOFF is en
> abled, XON = 11, XOFF = 13<7> - baud rate = 57600<7> - nothing to
> change...
>  - nothing to change...
>  - nothing to change...
>  - nothing to change...
> 
> *********** /etc/pcmcia/config.opts *****************
> include port 0xFE000000-0xFE0001FF
> include port 0xFE000400-0xFE0005FF
> include memory 0x80400000-0x807FFFFF
> include memory 0xBF8FF000-0xBFCFEFFF
> 
> 
> *********** iomem *****************
> ~ # cat /proc/iomem
> 80000000-fcffffff : PCI host bridge
>   80000000-80000fff : 0000:00:00.0
>   80400000-807fffff : PCI CardBus #02
>   bf8ff000-bfcfefff : PCI CardBus #02
>   bfcff000-bfcfffff : 0000:00:14.0
>     bfcff000-bfcfffff : yenta_socket
>   bfd00000-bfdfffff : PCI Bus #01
>   bfe00000-bfefffff : PCI Bus #01
>   bfff8000-bfffffff : 0000:00:10.0
>   fc004500-fc004507 : serial
> 
> *********** ioports *****************
> ~ # cat /proc/ioports
> fe000000-febfffff : PCI host bridge
>   fe000000-fe0001ff : PCI CardBus #02
>   fe000400-fe0005ff : PCI CardBus #02
>   febf9fc0-febf9fff : 0000:00:14.2
>   febfe000-febfefff : PCI Bus #01
>   febffff8-febfffff : 0000:00:10.0
> 
>  
> 
> 
> 
> 
> 
> _______________________________________________
> Linux PCMCIA reimplementation list
> http://lists.infradead.org/mailman/listinfo/linux-pcmcia


From dlclark at chtech.com  Thu Feb  8 18:24:36 2007
From: dlclark at chtech.com (David Clark)
Date: Thu, 8 Feb 2007 17:24:36 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070208211138.GA20710@isilmar.linta.de>
Message-ID: <002d01c74bd8$4ce4ca30$0f01a8c0@longhorn>

Something is not right!!!  Below is all I'm getting from lspcmcia
-vvv...one line.  I have a similar result with lspci -vvv except the one
line lists the pci controller.

"Socket 0 Bridge:        [yenta_cardbus]         (bus ID: 0000:00:14.0)"

Have you ever seen this before?  I'll get back to you after I look into
it further.

David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark at chtech.com
 

-----Original Message-----
From: Dominik Brodowski [mailto:linux at dominikbrodowski.net] 
Sent: Thursday, February 08, 2007 3:12 PM
To: David Clark
Cc: linux-pcmcia at lists.infradead.org
Subject: Re: Yenta Socket work with 32-bit card but not 16-bit

Hi,

What's the output of lspcmcia -vvv ?

	Dominik

On Thu, Feb 08, 2007 at 03:08:17PM -0600, David Clark wrote:
> I have a custom embedded board with a single PCMCIA slot.  The PCMCIA
> socket controller is a TI PCI1620 (Yenta).  The processor is a
Freescale
> MPC8245 (PowerPC 603e core).  I am running Linux kernel 2.6.14.2 and
> pcmciautils 014.
> 
> The PCMCIA slot works with a 32-bit network card that I have been
using
> during development.  It does not work with a 16-bit card.  When I plug
> the 16-bit card into the socket I get the message "cs: unable to map
> card memory"
> 
> I have searched many user groups, including this one, and I have
played
> with various settings in the config.opts file, to no avail.
Admittedly
> I don't have a good understanding of how pcmcia works in Linux so
> hopefully someone here can direct me.
> 
> Below are the outputs for (dmesg, config.opts, iomem and ioports).
> Please let me know if any further information would be helpful.  Thank
> you for your help.
> 
> David Clark
> Senior Software Engineer
> C&H Technologies, Inc
> Web: http:\\www.chtech.com
> Phone: 512-733-2621
> Fax: 512-733-2629
> Email: dlclark at chtech.com
> 
> 
> 
> *********** dmesg *****************
> dmesg
> Linux version 2.6.14.2ch1 (pcadmin at localhost.localdomain) (gcc version
> 3.4.1 200
> 40714 (TimeSys 3.4.1-7)) #250 PREEMPT Wed Feb 7 12:23:19 CST 2007
> Host bridge in Agent mode
> C&H VXI Intelligent Carrier Platform
> Port by C&H Technologies, Inc.
> On node 0 totalpages: 32768
>   DMA zone: 32768 pages, LIFO batch:15
>   Normal zone: 0 pages, LIFO batch:1
>   HighMem zone: 0 pages, LIFO batch:1
> Built 1 zonelists
> Kernel command line: root=/dev/ram rw console=ttyVXI
> ip=192.168.1.228:::255.255.
> 255.0:vx411c::off
> OpenPIC Version 1.2 (1 CPUs and 11 IRQ sources) at fc040000
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> time_init: decrementer frequency = 100.000000 MHz
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 125440k available (1644k kernel code, 496k data, 100k init, 0k
> highmem)
> Calibrating delay loop... 199.68 BogoMIPS (lpj=399360)
> Mount-cache hash table entries: 512
> checking if image is initramfs...it isn't (no cpio magic); looks like
an
> initrd
> Freeing initrd memory: 1856k freed
> softlockup thread 0 started up.
> NET: Registered protocol family 16
> PCI: Probing PCI hardware
> PCI: Scanning bus 0000:00
> PCI: Found 0000:00:00.0 [1057/0006] 000e00 00
> PCI: Calling quirk c000c184 for 0000:00:00.0
> PCI: Calling quirk c00c0f6c for 0000:00:00.0
> PCI: Calling quirk c00c0dec for 0000:00:00.0
> PCI: Found 0000:00:10.0 [12be/3042] 000e00 00
> PCI: Calling quirk c000c184 for 0000:00:10.0
> PCI: Calling quirk c00c0f6c for 0000:00:10.0
> PCI: Calling quirk c00c0dec for 0000:00:10.0
> PCI: Found 0000:00:13.0 [104c/ac23] 000604 01
> PCI: Calling quirk c000c184 for 0000:00:13.0
> PCI: Calling quirk c00c0f6c for 0000:00:13.0
> PCI: Calling quirk c00c0dec for 0000:00:13.0
> PCI: Found 0000:00:14.0 [104c/ac54] 000607 02
> PCI: Calling quirk c000c184 for 0000:00:14.0
> PCI: Calling quirk c00c0f6c for 0000:00:14.0
> PCI: Calling quirk c00c0dec for 0000:00:14.0
> PCI: Found 0000:00:14.2 [104c/8201] 000880 00
> PCI: Calling quirk c000c184 for 0000:00:14.2
> PCI: Calling quirk c00c0f6c for 0000:00:14.2
> PCI: Calling quirk c00c0dec for 0000:00:14.2
> PCI: Fixups for bus 0000:00
> PCI: Scanning behind PCI bridge 0000:00:13.0, config 010100, pass 0
> PCI: Scanning bus 0000:01
> PCI: Fixups for bus 0000:01
> PCI: Bus scan for 0000:01 returning with max=01
> PCI: Scanning behind PCI bridge 0000:00:14.0, config 020200, pass 0
> PCI: Scanning behind PCI bridge 0000:00:13.0, config 010100, pass 1
> PCI: Scanning behind PCI bridge 0000:00:14.0, config 020200, pass 1
> PCI: Bus scan for 0000:00 returning with max=05
> PCI: fixup irq: (0000:00:00.0) got 0
> PCI: fixup irq: (0000:00:10.0) got 20
> PCI: fixup irq: (0000:00:13.0) got 0
> PCI: fixup irq: (0000:00:14.0) got 19
> PCI: fixup irq: (0000:00:14.2) got 19
> PCI: Cannot allocate resource region 1 of device 0000:00:00.0
>   got res [80000000:80000fff] bus [80000000:80000fff] flags 200 for
BAR
> 1 of 000
> 0:00:00.0
> PCI: moved device 0000:00:00.0 resource 1 (200) to 80000000
> fsl-i2c.1: failed to claim resource 0
> unable to register device 0
> fsl-dma.0: failed to claim resource 0
> unable to register device 1
> fsl-dma.1: failed to claim resource 0
> unable to register device 2
> Registering openpic with sysfs...
> Generic PHY: Registered new driver
> PCI: Calling quirk c00c0cc0 for 0000:00:00.0
> PCI: Calling quirk c00c0cc0 for 0000:00:10.0
> PCI: Calling quirk c00c0cc0 for 0000:00:13.0
> PCI: Calling quirk c00c0cc0 for 0000:00:14.0
> PCI: Calling quirk c00c0cc0 for 0000:00:14.2
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
> disabled
> ttyS0 at MMIO 0xfc004500 (irq = 25) is a 16550A
> io scheduler noop registered
> io scheduler deadline registered
> RAMDISK driver initialized: 4 RAM disks of 32768K size 1024 blocksize
> QS6612: Registered new driver
> Yenta: CardBus bridge found at 0000:00:14.0 [0000:0000]
> PCI: Bus 2, cardbus bridge: 0000:00:14.0
>   IO window: 00000000-000001ff
>   IO window: 00000400-000005ff
>   PREFETCH window: bf8ff000-bfcfefff
>   MEM window: 80400000-807fffff
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:00:14.0, mfunc 0x00101000, devctl 0x66
> Yenta TI: socket 0000:00:14.0 probing PCI interrupt failed, trying to
> fix
> Yenta TI: socket 0000:00:14.0 falling back to parallel PCI interrupts
> Yenta TI: socket 0000:00:14.0 parallel PCI interrupts ok
> Yenta: ISA IRQ mask 0x0000, PCI irq 19
> Socket status: 30000410
> pcmcia: parent PCI bridge I/O window: 0xfe000000 - 0xfebfffff
> pcmcia: parent PCI bridge Memory window: 0x80000000 - 0xfcffffff
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 3, 32768 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> IP-Config: No network devices available.
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 100k init
> cs: memory probe 0x80000000-0xfcffffff:<7> - nothing to change...
>  - nothing to change...
>  excluding 0x80000000-0xfcffffff
> cs: unable to map card memory!
> cs: unable to map card memory!
>  - nothing to change...
>  - data bits = 8
>  - parity = none
>  - stop bits = 1
>  - RTS/CTS is disabled
>  - baud rate = 57600<7> - data bits = 7
>  - parity = none
>  - stop bits = 1
>  - RTS/CTS is disabled
>  - INBOUND XON/XOFF is enabled, XON = 11, XOFF = 13<7> - OUTBOUND
> XON/XOFF is en
> abled, XON = 11, XOFF = 13<7> - baud rate = 57600<7> - nothing to
> change...
>  - nothing to change...
>  - nothing to change...
>  - nothing to change...
> 
> *********** /etc/pcmcia/config.opts *****************
> include port 0xFE000000-0xFE0001FF
> include port 0xFE000400-0xFE0005FF
> include memory 0x80400000-0x807FFFFF
> include memory 0xBF8FF000-0xBFCFEFFF
> 
> 
> *********** iomem *****************
> ~ # cat /proc/iomem
> 80000000-fcffffff : PCI host bridge
>   80000000-80000fff : 0000:00:00.0
>   80400000-807fffff : PCI CardBus #02
>   bf8ff000-bfcfefff : PCI CardBus #02
>   bfcff000-bfcfffff : 0000:00:14.0
>     bfcff000-bfcfffff : yenta_socket
>   bfd00000-bfdfffff : PCI Bus #01
>   bfe00000-bfefffff : PCI Bus #01
>   bfff8000-bfffffff : 0000:00:10.0
>   fc004500-fc004507 : serial
> 
> *********** ioports *****************
> ~ # cat /proc/ioports
> fe000000-febfffff : PCI host bridge
>   fe000000-fe0001ff : PCI CardBus #02
>   fe000400-fe0005ff : PCI CardBus #02
>   febf9fc0-febf9fff : 0000:00:14.2
>   febfe000-febfefff : PCI Bus #01
>   febffff8-febfffff : 0000:00:10.0
> 
>  
> 
> 
> 
> 
> 
> _______________________________________________
> Linux PCMCIA reimplementation list
> http://lists.infradead.org/mailman/listinfo/linux-pcmcia



From linux at dominikbrodowski.net  Thu Feb  8 21:23:28 2007
From: linux at dominikbrodowski.net (Dominik Brodowski)
Date: Thu, 8 Feb 2007 21:23:28 -0500
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <002d01c74bd8$4ce4ca30$0f01a8c0@longhorn>
References: <20070208211138.GA20710@isilmar.linta.de>
	<002d01c74bd8$4ce4ca30$0f01a8c0@longhorn>
Message-ID: <20070209022328.GA7968@isilmar.linta.de>

Hi,

On Thu, Feb 08, 2007 at 05:24:36PM -0600, David Clark wrote:
> Something is not right!!!  Below is all I'm getting from lspcmcia
> -vvv...one line.  I have a similar result with lspci -vvv except the one
> line lists the pci controller.
> 
> "Socket 0 Bridge:        [yenta_cardbus]         (bus ID: 0000:00:14.0)"
> 
> Have you ever seen this before?  I'll get back to you after I look into
> it further.

It seems that in your case you need "pcmcia-socket-startup" to run -- which
is strange for a PPC. Normally, this call should be handled by udev, but you
might want to try out doing this call manually.

	Dominik


From cga2000 at optonline.net  Fri Feb  9 14:21:23 2007
From: cga2000 at optonline.net (cga2000)
Date: Fri, 09 Feb 2007 14:21:23 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070205070940.11415.qmail@cdy.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
	<20070205040658.GB1344@turki.gavron.org>
	<20070205070940.11415.qmail@cdy.org>
Message-ID: <20070209192123.GA1328@turki.gavron.org>

On Mon, Feb 05, 2007 at 02:09:40AM EST, Peter Stuge wrote:
> On Sun, Feb 04, 2007 at 11:06:58PM -0500, cga2000 wrote:
> > > > > >   product info: "3Com", "Megahertz 3CCFEM556", "LAN + 56k Modem", ""
> > > > > 
> > > > > This looks like a 32-bit CardBus card, not a 16-bit PCMCIA card.
> 
> The 3CCFEM556 is a 16-bit PCMCIA card, not a CardBus card.
> 
> 
> > > Possibly there's a PCI ID missing from the 3c59x driver.  What
> > > does lspci tell you about the card?  Do you have yenta_socket
> > > loaded so you can see the card in the slot?
> > 
> > Update:
> > 
> > rebooted the debian "etch" installer and tried the 3c59x driver but
> > am still getting the same result..
> 
> You're definately looking for the 3c574_cs driver in 2.6 kernels.
> 
> pcmcia-cs-3.2.8 comes with a .cis and a .dat file for this card, have
> you made the information within available to the 2.6 pcmcia drivers?
> See http://kernel.org/pub/linux/utils/kernel/pcmcia/howto.html under
> "2.5. The difficult cases: CIS overrides"
> (Basically copy 3CCFEM556.dat to /lib/firmware/3CCFEM556.cis)
> 
> 
> > are you suggesting that I might need a patched version so my modem/nic
> > combo is recognized?
> 
> I think it should just work.

It did.  :-)

With your excellent help, I should have been able to get this to work in
about an hour but ran into a problem with the KME/SCSI card in the other
slot that caused booting into my new install to fail.

>From the messages before the crash, I eventually figured out that the
problem was likely with this other card, so I physically removed it and
was able to do a clean install.

Since I wasn't sure where to look for the correct version of
3CCFEM556.dat, I told the installer that I didn't have a network card,
rebooted into the new system .. found a 3CCFEM556.dat file in the /etc
tree .. pcmcia Version 3.2.8, IIRC, copied/renamed it to /lib/firmware
as 3CCFEM556.cis .. rebooted .. and sure enough "ifconfig -a" and other
tell-tale signs such as boot-up messages and the light on the NIC's
dongle coming on .. showed that the card had been recognized. 

After that it was just a matter of running dhclient to bring up eth0.

I needed to add the magical "auto eth0" and "iface eth0 inet dhcp" to
/etc/network/interfaces to ensure that all this is done automatically
when I reboot .. and that was it.

It just worked.

I could kick myself for wasting so much time over what turns out to be a
trivial problem.  Once you know the solution of course.

:-)

Can't thank you enough for your help.

Thanks,

cga


From stuge-linux-pcmcia at cdy.org  Sat Feb 10 21:01:21 2007
From: stuge-linux-pcmcia at cdy.org (Peter Stuge)
Date: Sun, 11 Feb 2007 03:01:21 +0100
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070209192123.GA1328@turki.gavron.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
	<20070205040658.GB1344@turki.gavron.org>
	<20070205070940.11415.qmail@cdy.org>
	<20070209192123.GA1328@turki.gavron.org>
Message-ID: <20070211020121.16453.qmail@cdy.org>

On Fri, Feb 09, 2007 at 02:21:23PM -0500, cga2000 wrote:
> Since I wasn't sure where to look for the correct version of
> 3CCFEM556.dat

I don't think the CIS files have changed a lot over time. They're
bound to the hardware so they either work with a card or not.


>, I told the installer that I didn't have a network card,
> rebooted into the new system .. found a 3CCFEM556.dat file in the
> /etc tree .. pcmcia Version 3.2.8, IIRC, copied/renamed it to
> /lib/firmware as 3CCFEM556.cis .. rebooted .. and sure enough
> "ifconfig -a" and other tell-tale signs such as boot-up messages
> and the light on the NIC's dongle coming on .. showed that the card
> had been recognized. 

Right. This means that the kernel PCMCIA configuration is in order..


> After that it was just a matter of running dhclient to bring up eth0.
> 
> I needed to add the magical "auto eth0" and "iface eth0 inet dhcp"
> to /etc/network/interfaces to ensure that all this is done
> automatically when I reboot .. and that was it.

..and this part depends on the particular distribution.


> I could kick myself for wasting so much time over what turns out to
> be a trivial problem.  Once you know the solution of course.

It was documented though. Whoever created the netinstall system
should have taken more care to make PCMCIA work right. Also it shows
that reading docs helps if one is stuck. :)


> Can't thank you enough for your help.

You're welcome. I'm glad that it works.


//Peter


From stuge-linux-pcmcia at cdy.org  Sat Feb 10 21:02:42 2007
From: stuge-linux-pcmcia at cdy.org (Peter Stuge)
Date: Sun, 11 Feb 2007 03:02:42 +0100
Subject: Why separate CIS files in 2.6?
Message-ID: <20070211020242.16625.qmail@cdy.org>

Why not include them within the drivers in 2.6? Licensing?


//Peter


From adobriyan at gmail.com  Sun Feb 11 03:16:36 2007
From: adobriyan at gmail.com (Alexey Dobriyan)
Date: Sun, 11 Feb 2007 11:16:36 +0300
Subject: [PATCH] pcmcia: some class_device fallout
Message-ID: <20070211081636.GB16712@martell.zuzino.mipt.ru>

As found on some arm defconfigs.

I only looked at how original patch changes things and other patches fix
compilation. ;-)

Signed-off-by: Alexey Dobriyan <adobriyan at gmail.com>
---

 drivers/pcmcia/at91_cf.c    |    2 +-
 drivers/pcmcia/soc_common.c |    8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

--- a/drivers/pcmcia/soc_common.c
+++ b/drivers/pcmcia/soc_common.c
@@ -478,7 +478,7 @@ dump_bits(char **p, const char *prefix, 
  *
  * Returns: the number of characters added to the buffer
  */
-static ssize_t show_status(struct device *dev, char *buf)
+static ssize_t show_status(struct device *dev, struct device_attribute *attr, char *buf)
 {
 	struct soc_pcmcia_socket *skt =
 		container_of(dev, struct soc_pcmcia_socket, socket.dev);
@@ -501,7 +501,7 @@ static ssize_t show_status(struct device
 
 	return p-buf;
 }
-static CLASS_DEVICE_ATTR(status, S_IRUGO, show_status, NULL);
+static DEVICE_ATTR(status, S_IRUGO, show_status, NULL);
 
 
 static struct pccard_operations soc_common_pcmcia_operations = {
@@ -660,7 +660,7 @@ int soc_common_drv_pcmcia_probe(struct d
 
 		skt->socket.ops = &soc_common_pcmcia_operations;
 		skt->socket.owner = ops->owner;
-		skt->socket.dev.dev = dev;
+		skt->socket.dev.parent = dev;
 
 		init_timer(&skt->poll_timer);
 		skt->poll_timer.function = soc_common_pcmcia_poll_event;
@@ -747,7 +747,7 @@ int soc_common_drv_pcmcia_probe(struct d
 
 		add_timer(&skt->poll_timer);
 
-		device_create_file(&skt->socket.dev, &device_attr_status);
+		device_create_file(&skt->socket.dev, &dev_attr_status);
 	}
 
 	dev_set_drvdata(dev, sinfo);
--- a/drivers/pcmcia/at91_cf.c
+++ b/drivers/pcmcia/at91_cf.c
@@ -278,7 +278,7 @@ static int __init at91_cf_probe(struct p
 		board->det_pin, board->irq_pin);
 
 	cf->socket.owner = THIS_MODULE;
-	cf->socket.dev.dev = &pdev->dev;
+	cf->socket.dev.parent = &pdev->dev;
 	cf->socket.ops = &at91_cf_ops;
 	cf->socket.resource_ops = &pccard_static_ops;
 	cf->socket.features = SS_CAP_PCCARD | SS_CAP_STATIC_MAP



From cga2000 at optonline.net  Sun Feb 11 04:39:48 2007
From: cga2000 at optonline.net (cga2000)
Date: Sun, 11 Feb 2007 04:39:48 -0500
Subject: 3c574 NIC support with recent 2.6 kernels.
In-Reply-To: <20070211020121.16453.qmail@cdy.org>
References: <20070204190031.GI14439@turki.gavron.org>
	<20070204220448.GZ7585@parisc-linux.org>
	<20070204225533.GM14439@turki.gavron.org>
	<20070205023024.GA7585@parisc-linux.org>
	<20070205040658.GB1344@turki.gavron.org>
	<20070205070940.11415.qmail@cdy.org>
	<20070209192123.GA1328@turki.gavron.org>
	<20070211020121.16453.qmail@cdy.org>
Message-ID: <20070211093947.GJ794@turki.gavron.org>

On Sat, Feb 10, 2007 at 09:01:21PM EST, Peter Stuge wrote:
> On Fri, Feb 09, 2007 at 02:21:23PM -0500, cga2000 wrote:
> > Since I wasn't sure where to look for the correct version of
> > 3CCFEM556.dat
> 
> I don't think the CIS files have changed a lot over time. They're
> bound to the hardware so they either work with a card or not.

Yes. The sarge and etch files are identical.
 
> >, I told the installer that I didn't have a network card, rebooted
> >into the new system .. found a 3CCFEM556.dat file in the /etc tree ..
> >pcmcia Version 3.2.8, IIRC, copied/renamed it to /lib/firmware as
> >3CCFEM556.cis .. rebooted .. and sure enough "ifconfig -a" and other
> >tell-tale signs such as boot-up messages and the light on the NIC's
> >dongle coming on .. showed that the card had been recognized. 

> Right. This means that the kernel PCMCIA configuration is in order..

Yes.  I was having problems with my other PC card and that made it more
difficult to think clearly.  The correct way to work around the problem
with the "etch" installer is obviously to switch to a console and fix
the problem before the installer attempts to detect your NIC.  That way,
the network is configured automatically and your box goes online after
you boot into the new system.  Hopefully, you saw my attempt to update
my old bug report and you are already aware of this.

> > After that it was just a matter of running dhclient to bring up eth0.
> > 
> > I needed to add the magical "auto eth0" and "iface eth0 inet dhcp"
> > to /etc/network/interfaces to ensure that all this is done
> > automatically when I reboot .. and that was it.
> 
> ..and this part depends on the particular distribution.

Yes. 

And as explained above where debian etch is concerned this is not really
necessary.

> > I could kick myself for wasting so much time over what turns out to
> > be a trivial problem.  Once you know the solution of course.
> 
> It was documented though. Whoever created the netinstall system
> should have taken more care to make PCMCIA work right. Also it shows
> that reading docs helps if one is stuck. :)

mea culpa ..

I think that the reason I missed the relevance of the 2.6 kernel pcmcia
doc was that I never expected this not to work in the first place since
I had done many installs on this system .. starting with RedHat 6.2 or
thereabout some seven years ago and never experienced a problem with
this card.  

Hence, I am pretty sure that I initially read through the "mini HOWTO"
but I didn't pay too much attention to the "hard cases" thinking this
was probably not worth looking into.  

I may also have approached this with the wrong mental attitude .. put
too much trust in the sacrosanct debian installer and its maintainers ..
or worse, maybe I was a little frustrated with my inability to address
the issue and somewhere deep down I blamed other folks and expected
someone to fix it for me. 

Thank goodness I still have a golden opportunity to make amends.  

:-)

I still need that KME/SCSI card and the "turtle ninja" driver to work so
I have some means to back up my system before it goes into "production".

It should be easier as far as "mental attitude" goes .. since I don't
expect this one to work out of the box .. but I do expect it to  be a
bit harder "technically".

Thanks again for your help.

cga.


From akohlsmith-pcmcia at benshaw.com  Mon Feb 12 15:02:12 2007
From: akohlsmith-pcmcia at benshaw.com (Andrew Kohlsmith)
Date: Mon, 12 Feb 2007 15:02:12 -0500
Subject: new driver, yenta_socket and interrupts
Message-ID: <200702121502.12374.akohlsmith-pcmcia@benshaw.com>

Good day, everyone,

I've been writing a device driver for the SST 5136-DNP PCMCIA CAN/DeviceNet 
board.  I'm developing on a stock 2.6.19 (Slackware 11 system).

I have the card working fine without interrupts.  I can successfully 
communicate with the card and the CAN network it's connected to.  It's now 
time, however, to get interrupts working, and I've run up against a barrier I 
just can't seem to get beyond.

I cannot seem to get the interrupt routine to work.  I either softlock the 
system or cause an unserviced interrupt storm which causes the kernel to shut 
down the yenta_socket IRQ altogether.

My IRQ handler is dirt-stupid-simple at this point:
static irqreturn_t ss5136dn_isr(int irq, void *dev_id)
{
	ss5136dn_dev_t *dev = (ss5136dn_dev_t *)dev_id;
	u8 b;
	
	if(!dev)
		return IRQ_NONE;

	if (!(dev->p_dev->_locked))
		return IRQ_HANDLED;

	spin_lock(&dev->lock);

	b = inb(dev->portbase + BCR0);
	outb(b | 0x04, dev->portbase + BCR0);

	spin_unlock(&dev->lock);

	return IRQ_HANDLED;
}

(I have some printk()s in there I've removed, but that's really all I have in 
here.)

My _config() routine is pretty much ripped right out of one of the existing 
PCMCIA char drivers; it parses the tuples until it finds an IO region it can 
successfully request, and then requests the IRQ and finally a configuration 
lock.

The IRQ requesting part is what's causing the trouble:
	if (link->conf.Attributes & CONF_ENABLE_IRQ) {
		link->irq.Attributes = IRQ_TYPE_DYNAMIC_SHARING | IRQ_FIRST_SHARED | 
IRQ_HANDLE_PRESENT;
		link->irq.IRQInfo1 = IRQ_LEVEL_ID | IRQ_SHARE_ID;
		link->irq.Handler     = ss5136dn_isr;
		link->irq.Instance    = dev;
		CS_CHECK(RequestIRQ, pcmcia_request_irq(link, &link->irq));
		dev->irq = link->irq.AssignedIRQ;
		}

	link->conf.IntType = INT_MEMORY_AND_IO;
	CS_CHECK(RequestConfiguration, pcmcia_request_configuration(link, 
&link->conf));

	dev->portbase = link->io.BasePort1;	/* needed by ss5136dn_hwinit() */
	dev->memoffset = map.CardOffset;

	rc = ss5136dn_hwinit(dev);

Shortly after pcmcia_request_configuration() is called, I get a soft lockup.  
The backtrace indicates that I never get to my hardware init routine:

ss5136dn_cs: ss5136dn_config(0xc15b7000), dev @ 0xdf997980
BUG: soft lockup detected on CPU#0!
 [<c0141bb1>] softlockup_tick+0xa1/0xd0
 [<c01292c6>] update_process_times+0x76/0xb0
 [<c0106a78>] timer_interrupt+0x48/0xd0
 [<c0142365>] handle_IRQ_event+0x25/0x60
 [<c0143660>] handle_level_irq+0x90/0x130
 [<c0105863>] do_IRQ+0x53/0xa0
 [<c0103bda>] common_interrupt+0x1a/0x20
 [<c014235e>] handle_IRQ_event+0x1e/0x60
 [<c0143660>] handle_level_irq+0x90/0x130
 [<c0105863>] do_IRQ+0x53/0xa0
 [<c0103bda>] common_interrupt+0x1a/0x20
 [<c0124723>] __do_softirq+0x43/0xb0
 [<c01247bd>] do_softirq+0x2d/0x30
 [<c01247f7>] irq_exit+0x37/0x40
 [<c0105868>] do_IRQ+0x58/0xa0
 [<c0103bda>] common_interrupt+0x1a/0x20
 [<c0276004>] delay_tsc+0x14/0x20
 [<c0276046>] __delay+0x6/0x10
 [<e115b72b>] pcmcia_request_configuration+0x14b/0x3e0 [pcmcia]
 [<e115bbac>] pcmcia_request_irq+0xdc/0x120 [pcmcia]
 [<e12151a3>] ss5136dn_config+0x473/0x650 [ss5136dn_cs]
 [<c013882c>] clocksource_get_next+0x3c/0x70
 [<c01288f8>] change_clocksource+0x18/0x170
 [<c01288f8>] change_clocksource+0x18/0x170
 [<c012944b>] run_timer_softirq+0x13b/0x200
 [<c0124756>] __do_softirq+0x76/0xb0
 [<c0275393>] vsnprintf+0x2f3/0x560
 [<c011ffee>] release_console_sem+0xae/0x120
 [<c011fd28>] vprintk+0x1c8/0x2f0
 [<c011a471>] __activate_task+0x21/0x40
 [<c011a67a>] try_to_wake_up+0x4a/0xf0
 [<c013882c>] clocksource_get_next+0x3c/0x70
 [<c01288f8>] change_clocksource+0x18/0x170
 [<c011a471>] __activate_task+0x21/0x40
 [<c013882c>] clocksource_get_next+0x3c/0x70
 [<c01288f8>] change_clocksource+0x18/0x170
 [<c01288f8>] change_clocksource+0x18/0x170
 [<c012944b>] run_timer_softirq+0x13b/0x200
 [<c0124756>] __do_softirq+0x76/0xb0
 [<c0275393>] vsnprintf+0x2f3/0x560
 [<c011ffee>] release_console_sem+0xae/0x120
 [<c011fd28>] vprintk+0x1c8/0x2f0
 [<c011a471>] __activate_task+0x21/0x40
 [<c011a67a>] try_to_wake_up+0x4a/0xf0
 [<e1215437>] ss5136dn_probe+0x97/0xe0 [ss5136dn_cs]
 [<c02720df>] kobject_get+0xf/0x20
 [<e1159445>] pcmcia_device_probe+0xa5/0x170 [pcmcia]
 [<c02f9345>] really_probe+0xb5/0x110
 [<c02f9488>] driver_probe_device+0xc8/0xd0
 [<c03e7d39>] klist_next+0x69/0xe0
 [<c02f87aa>] bus_for_each_drv+0x3a/0x60
 [<c02f94ed>] device_attach+0x4d/0x70
 [<c02f9490>] __device_attach+0x0/0x10
 [<c02f8a26>] bus_attach_device+0x26/0x60
 [<c02f7203>] device_add+0x1a3/0x3f0
 [<e1159ad4>] pcmcia_device_add+0x1e4/0x290 [pcmcia]
 [<e1159c1a>] pcmcia_card_add+0x9a/0xc0 [pcmcia]
 [<c011fd28>] vprintk+0x1c8/0x2f0
 [<c02720df>] kobject_get+0xf/0x20
 [<e084e156>] pcmcia_get_socket+0x56/0xa0 [pcmcia_core]
 [<e115a7a8>] ds_event+0x68/0xb0 [pcmcia]
 [<e084e66e>] send_event+0x9e/0x140 [pcmcia_core]
 [<e084eb7c>] socket_insert+0xdc/0x170 [pcmcia_core]
 [<e084edc6>] socket_detect_change+0x56/0x70 [pcmcia_core]
 [<e084ef77>] pccardd+0x197/0x230 [pcmcia_core]
 [<c03e8391>] schedule+0x331/0x6a0
 [<c011b1f0>] default_wake_function+0x0/0x10
 [<c011b1f0>] default_wake_function+0x0/0x10
 [<e084ede0>] pccardd+0x0/0x230 [pcmcia_core]
 [<c0133d65>] kthread+0xa5/0xe0
 [<c0133cc0>] kthread+0x0/0xe0
 [<c0103d53>] kernel_thread_helper+0x7/0x14
 =======================
ss5136dn_cs: ss5136dn_shutdown(0xdf997980)<6>ss5136dn_cs: Card failed "are you 
there" test.
ss5136dn_cs: ss5136dn_shutdown(0xdf997980)<6>ss5136dn_cs: ss5136dn_reset 
returned failure code -1
ss5136dn_cs: ss5136dn_hwinit failed (-1)
ss5136dn_cs: ss5136dn_shutdown(0xdf997980)<7>ss5136dn_cs: 
ss5136dn_try_to_release(0xdf997980)
pccard: card ejected from slot 0

If I set link->irq.Handler to NULL and do not set the IRQ_HANDLE_PRESENT bit 
in link->irq.Attributes, I run into the situation where the kernel shuts down 
the IRQ altogether (thus killing any further development until I reboot since 
I can no longer see yenta interrupts for card insertion/removal).

I was using a NULL handler in the hopes of getting the IRQ set up, but unused, 
so I could call my hwinit() routine and then, after hwinit(), call 
pcmcia_modify_configuration with link->irq.Attributes |= IRQ_HANDLE_PRESENT 
and link->irq.Handler = ss5136dn_isr.  Unfortunately that didn't work.  :-)

I also tried IRQ_PULSE_ID, rationalizing that the PCMCIA subsystem is really 
ISA-based and ISA interrupts were all edge-triggered.  This didn't do 
anything useful, either.

Now digging through the 2.6.18 (http://lxr.linux.no doesn't have 2.6.19 up 
yet) kernel source and looking at the pcmcia_request_irq() routine, I see 
that so long as IRQ_HANDLE_PRESENT is set, my handler and my instance data 
should be correct.  However I get an interrupt before my hardware's even been 
configured, and since my dev structure isn't initialized, I can't clear the 
interrupt if it really is my card that's causing it (since no other handler 
seems to be claiming it).

Some of my earlier debugging in the interrupt handler showed that as soon as 
pcmcia_request_configuration() was called, my interrupt handler got hit, but 
the configuration was not locked yet.  I was returning IRQ_HANDLED though, so 
it should have been fine.  On a whim, I returned IRQ_NONE in that case (i.e. 
if (!(dev->p_dev->_locked))) and that promptly caused the kernel to shut down 
the IRQ line.  :-)  I also tried setting the IRQ flags for exclusive IRQ 
access, but I just got a runtime warning that it couldn't grant IRQ 
exclusivity and to update my driver.

This is all on a Compaq Evo N160 with a TI PCI1410 controller.  lspci -vvv 
output looks like this:
# lspci -vvv -s 2:06.0
02:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller 
(rev 01)
        Subsystem: Compaq Computer Corporation Unknown device b103
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 168, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at d0202000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
        Memory window 0: 30000000-31fff000 (prefetchable)
        Memory window 1: 34000000-35fff000
        I/O window 0: 00003400-000034ff
        I/O window 1: 00003800-000038ff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt- PostWrite+
        16-bit legacy interface ports at 0001

I'm not running any special kernel parameters for BIOS or APIC IRQ routing, 
it's all pretty stock.

Oh yeah -- I also tried to initialize my hardware BEFORE 
pcmcia_request_configuration() ran, to see if I could set up the hardware 
interrupts, clear any pending ones and THEN get the PCMCIA system to lock 
down the configuration, but (obviously, in hindsight) I couldn't access my 
card until the PCMCIA configuration was done.

Can anyone assist me?

Regards,
Andrew


From dlclark at chtech.com  Tue Feb 13 10:25:08 2007
From: dlclark at chtech.com (David Clark)
Date: Tue, 13 Feb 2007 09:25:08 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070208211138.GA20710@isilmar.linta.de>
Message-ID: <001601c74f83$255d4c90$0f01a8c0@longhorn>

> What's the output of lspcmcia -vvv ?

Below are the outputs of both lspcmcia -vvv and lspci -vvv.  

One important note is that on our board we are only using slot A of the
PCI1620.  Slot B is not physically connected and is explicitly disabled
in the bootloader.  

The one thing that jump out at me from the following lspcmcia output is
the Available iomem from Socket 0 being equal to "--none--".


*********  lspcmcia -vvv  *********************
lspcmcia -vvv
Socket 0 Bridge:   	[yenta_cardbus] 	(bus ID: 0000:00:14.0)
	Configuration:	state: suspended	ready: yes
			Voltage: 5.0V Vcc: 5.0V Vpp: 5.0V
			Available IRQs: none
			Available ioports:	0xfe000000 - 0xfebfffff
			Available iomem:	--none--
Socket 1 Bridge:   	[yenta_cardbus] 	(bus ID: 0000:00:14.1)
	Configuration:	state: suspended	ready: yes
			Available IRQs: none
			Available ioports:	0xfe000000 - 0xfebfffff
			Available iomem:	0x80000000 - 0xfcffffff



*********  lspci -vvv  *********************
~ # lspci -vvv
00:00.0 Host bridge: Motorola MPC8245 [Unity] (rev 14)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr-Step
ping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- 
<MAbort+ >SERR- <PERR-
	Latency: 64, Cache Line Size 08
	Interrupt: pin A routed to IRQ 0
	Region 0: Memory at <unassigned> (32-bit, prefetchable)
	Region 2: Memory at <unassigned> (32-bit, prefetchable)

00:10.0 I2O: Anchor Chips Inc. AN3042Q CO-MEM Lite (rev 02) (prog-if 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128, Cache Line Size 08
	Interrupt: pin ? routed to IRQ 20
	Region 0: Memory at 00000000bfff8000 (32-bit, non-prefetchable)
[size=32
K]
	Region 1: I/O ports at bffff8 [size=8]

00:12.0 Ethernet controller: Digital Equipment Corporation DECchip
21142/43 (rev
 41)
	Subsystem: Unknown device 0400:0001
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128 (5000ns min, 10000ns max), Cache Line Size 08
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at bfff00 [size=128]
	Region 1: Memory at 00000000bfff7c00 (32-bit, non-prefetchable)
[size=1K
]
	Expansion ROM at 00000000dfbc0000 [disabled] [size=256K]

00:13.0 PCI bridge: Texas Instruments PCI2250 PCI-to-PCI Bridge (rev 02)
(prog-i
f 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128, Cache Line Size 08
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=128
	I/O behind bridge: 00bfe000-00bfefff
	Memory behind bridge: bfe00000-bfefffff
	Prefetchable memory behind bridge: bfd00000-bfdfffff
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:14.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 168, Cache Line Size 08
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at 00000000bfcff000 (32-bit, non-prefetchable)
[size=4K
]
	Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
	Memory window 0: bf8ff000-bfcfe000 (prefetchable)
	Memory window 1: 80000000-803ff000
	I/O window 0: 00000000-000001ff
	I/O window 1: 00000400-000005ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
	16-bit legacy interface ports at 0001

00:14.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 168, Cache Line Size 08
	Interrupt: pin B routed to IRQ 0
	Region 0: Memory at 00000000bf8fe000 (32-bit, non-prefetchable)
[size=4K
]
	Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
	Memory window 0: bf4fe000-bf8fd000 (prefetchable)
	Memory window 1: 80400000-807ff000
	I/O window 0: 00000800-000009ff
	I/O window 1: 00000c00-00000dff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt-
PostWrite+
	16-bit legacy interface ports at 0001

00:14.2 System peripheral: Texas Instruments PCI1620 Firmware Loading
Function (
rev 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128 (1750ns min, 1000ns max), Cache Line Size 08
	Interrupt: pin ? routed to IRQ 19
	Region 0: I/O ports at bf5fc0 [size=64]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

~ #




From dlclark at chtech.com  Tue Feb 13 10:25:17 2007
From: dlclark at chtech.com (David Clark)
Date: Tue, 13 Feb 2007 09:25:17 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070209022328.GA7968@isilmar.linta.de>
Message-ID: <001701c74f83$2ad71fc0$0f01a8c0@longhorn>

> It seems that in your case you need "pcmcia-socket-startup" to run --
which
> is strange for a PPC. Normally, this call should be handled by udev,
but you
> might want to try out doing this call manually.

>	Dominik


pcmcia-socket-startup does not seem to any effect on the situation.



From dlclark at chtech.com  Thu Feb 15 11:13:52 2007
From: dlclark at chtech.com (David Clark)
Date: Thu, 15 Feb 2007 10:13:52 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070209022328.GA7968@isilmar.linta.de>
Message-ID: <000101c7511c$49a2ab00$0f01a8c0@longhorn>

Do I need to somehow tell the kernel to reserve a block of PCI memory
space just for 16 PCMCIA cards?  Is this what the "config.opts" file is
supposed to do?

I've been staring at source for a couple of days now, trying to
understand how this all works and it is slow going.

Any hints?

David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark at chtech.com
 

-----Original Message-----
From: Dominik Brodowski [mailto:linux at dominikbrodowski.net] 
Sent: Thursday, February 08, 2007 8:23 PM
To: David Clark
Cc: linux-pcmcia at lists.infradead.org
Subject: Re: Yenta Socket work with 32-bit card but not 16-bit

Hi,

On Thu, Feb 08, 2007 at 05:24:36PM -0600, David Clark wrote:
> Something is not right!!!  Below is all I'm getting from lspcmcia
> -vvv...one line.  I have a similar result with lspci -vvv except the
one
> line lists the pci controller.
> 
> "Socket 0 Bridge:        [yenta_cardbus]         (bus ID:
0000:00:14.0)"
> 
> Have you ever seen this before?  I'll get back to you after I look
into
> it further.

It seems that in your case you need "pcmcia-socket-startup" to run --
which
is strange for a PPC. Normally, this call should be handled by udev, but
you
might want to try out doing this call manually.

	Dominik



From jar at pcuf.fi  Thu Feb 15 11:18:18 2007
From: jar at pcuf.fi (Jar)
Date: Thu, 15 Feb 2007 18:18:18 +0200
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <000101c7511c$49a2ab00$0f01a8c0@longhorn>
References: <000101c7511c$49a2ab00$0f01a8c0@longhorn>
Message-ID: <45D487CA.7010403@pcuf.fi>

David Clark wrote:
> Do I need to somehow tell the kernel to reserve a block of PCI memory
> space just for 16 PCMCIA cards?  Is this what the "config.opts" file is
> supposed to do?
> 
> I've been staring at source for a couple of days now, trying to
> understand how this all works and it is slow going.
> 
> Any hints?

Did you run 'pcmcia-socket-startup' as Dominik suggested?


-- 
Best Regards, Jar


From dlclark at chtech.com  Thu Feb 15 11:22:42 2007
From: dlclark at chtech.com (David Clark)
Date: Thu, 15 Feb 2007 10:22:42 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <45D487CA.7010403@pcuf.fi>
Message-ID: <000701c7511d$8561d070$0f01a8c0@longhorn>

Jar wrote:
> Did you run 'pcmcia-socket-startup' as Dominik suggested?

Yes, and it doesn't seem to have any effect on the situation.

David




From dlclark at chtech.com  Thu Feb 15 13:18:20 2007
From: dlclark at chtech.com (David Clark)
Date: Thu, 15 Feb 2007 12:18:20 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <000701c7511d$8561d070$0f01a8c0@longhorn>
Message-ID: <000b01c7512d$acbe2870$0f01a8c0@longhorn>

I see the following lines in my dmesg output.

"cs: memory probe 0x80000000-0xfcffffff"
"	excluding 0x80000000-0xfcffffff"

I may be way off track here and pleasae tell me if so.  From looking at
the source code in "rsrc_nonstatic.c" I gather that the first time the
socket comes up, the kernel probes (do_mem_probe()) the PCI memory space
to find a suitable memory region which can be allocated to the PCMCIA
cards.  

In my case 0x80000000-0xfcffffff is the entire memory range available to
the host PCI bridge.  Not all of this memory range is allocated to the
various PCI devices, so why then does the memory probe not find any
available resources?

Is this potentially related to my problem?  Again I'm trying my best to
understand how this all works.

Thanks,

David



********   /proc/iomem   ********
~ # cat /proc/iomem
80000000-fcffffff : PCI host bridge
  80000000-803fffff : PCI CardBus #02
  bf8ff000-bfcfefff : PCI CardBus #02
  bfcff000-bfcfffff : 0000:00:14.0
    bfcff000-bfcfffff : yenta_socket
  bfd00000-bfdfffff : PCI Bus #01
  bfe00000-bfefffff : PCI Bus #01
  bfff7c00-bfff7fff : 0000:00:12.0
    bfff7c00-bfff7fff : tulip
  bfff8000-bfffffff : 0000:00:10.0
  fc004500-fc004507 : serial
~ #



********   lspci -vvv   ********
~ # lspci -vvv
00:00.0 Host bridge: Motorola MPC8245 [Unity] (rev 14)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- 
<MAbort+ >SERR- <PERR-
	Latency: 64, Cache Line Size 08
	Interrupt: pin A routed to IRQ 0
	Region 0: Memory at <unassigned> (32-bit, prefetchable)
	Region 2: Memory at <unassigned> (32-bit, prefetchable)

00:10.0 I2O: Anchor Chips Inc. AN3042Q CO-MEM Lite (rev 02) (prog-if 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128, Cache Line Size 08
	Interrupt: pin ? routed to IRQ 20
	Region 0: Memory at 00000000bfff8000 (32-bit, non-prefetchable)
[size=32
K]
	Region 1: I/O ports at bffff8 [size=8]

00:12.0 Ethernet controller: Digital Equipment Corporation DECchip
21142/43 (rev
 41)
	Subsystem: Unknown device 0400:0001
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128 (5000ns min, 10000ns max), Cache Line Size 08
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at bfff00 [size=128]
	Region 1: Memory at 00000000bfff7c00 (32-bit, non-prefetchable)
[size=1K
]
	Expansion ROM at 00000000dfbc0000 [disabled] [size=256K]

00:13.0 PCI bridge: Texas Instruments PCI2250 PCI-to-PCI Bridge (rev 02)
(prog-i
f 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128, Cache Line Size 08
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=128
	I/O behind bridge: 00bfe000-00bfefff
	Memory behind bridge: bfe00000-bfefffff
	Prefetchable memory behind bridge: bfd00000-bfdfffff
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:14.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 168, Cache Line Size 08
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at 00000000bfcff000 (32-bit, non-prefetchable)
[size=4K
]
	Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
	Memory window 0: bf8ff000-bfcfe000 (prefetchable)
	Memory window 1: 80000000-803ff000
	I/O window 0: 00000000-000001ff
	I/O window 1: 00000400-000005ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
	16-bit legacy interface ports at 0001

00:14.2 System peripheral: Texas Instruments PCI1620 Firmware Loading
Function (
rev 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
	Latency: 128 (1750ns min, 1000ns max), Cache Line Size 08
	Interrupt: pin ? routed to IRQ 19
	Region 0: I/O ports at bf9fc0 [size=64]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-






From linux at dominikbrodowski.net  Thu Feb 15 13:29:07 2007
From: linux at dominikbrodowski.net (Dominik Brodowski)
Date: Thu, 15 Feb 2007 13:29:07 -0500
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <000b01c7512d$acbe2870$0f01a8c0@longhorn>
References: <000701c7511d$8561d070$0f01a8c0@longhorn>
	<000b01c7512d$acbe2870$0f01a8c0@longhorn>
Message-ID: <20070215182907.GA26928@isilmar.linta.de>

Hi,

On Thu, Feb 15, 2007 at 12:18:20PM -0600, David Clark wrote:
> I may be way off track here and pleasae tell me if so.  From looking at
> the source code in "rsrc_nonstatic.c" I gather that the first time the
> socket comes up, the kernel probes (do_mem_probe()) the PCI memory space
> to find a suitable memory region which can be allocated to the PCMCIA
> cards.  

Right. Such mem resources are needed to access the card "CIS", too, which in
turn is required to correctly determine which card this is.

> In my case 0x80000000-0xfcffffff is the entire memory range available to
> the host PCI bridge.  Not all of this memory range is allocated to the
> various PCI devices, so why then does the memory probe not find any
> available resources?

Good question -- to which I don't really have an answer, unfortunately.
Could you try out what happens if you disable "CONFIG_ISA" in your kernel
config (which in turn should switch of CONFIG_PCMCIA_PROBE)?

> Is this potentially related to my problem?  Again I'm trying my best to
> understand how this all works.

Most likely this is the root of the problem.

	Dominik


From dlclark at chtech.com  Thu Feb 15 15:44:58 2007
From: dlclark at chtech.com (David Clark)
Date: Thu, 15 Feb 2007 14:44:58 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070215182907.GA26928@isilmar.linta.de>
Message-ID: <001301c75142$28bdb080$0f01a8c0@longhorn>


> Could you try out what happens if you disable "CONFIG_ISA" in your
kernel
> config (which in turn should switch of CONFIG_PCMCIA_PROBE)?

I have been running with both CONFIG_ISA and CONFIG_PCMCIA_PROBE
disabled.  In fact, I can't seem to find the corresponding options in
menuconfig.

> Most likely this is the root of the problem.

Great, at least I'm making progress.


Not sure if this is related but one thing I just noticed is that
allocated PCI resources stop at 0xBFFFFFFF, excluding the serial device
which is part of the processor Embedded Utilities Memory Block (EUMB)
which is explicitly set at 0xfc000000.  If I recall correctly, the PCI
bus resources are assigned starting with the high addresses and working
downwards.  Therefore the highest PCI address is 0xbfffffff.  The kernel
is configured to start at 0xc0000000; however, this is a virtual address
corresponding to physical address 0.  Is there a correlation or is it
just coincidence that the pci devices end at 0xbfffffff and the kernel
starts at 0xc0000000.  Note that there is a gap of available space
between 0x80400000 and 0xbf8fefff.


/proc/iomem
80000000-fcffffff : PCI host bridge
  80000000-803fffff : PCI CardBus #02
  bf8ff000-bfcfefff : PCI CardBus #02
  bfcff000-bfcfffff : 0000:00:14.0
    bfcff000-bfcfffff : yenta_socket
  bfd00000-bfdfffff : PCI Bus #01
  bfe00000-bfefffff : PCI Bus #01
  bfff7c00-bfff7fff : 0000:00:12.0
    bfff7c00-bfff7fff : tulip
  bfff8000-bfffffff : 0000:00:10.0
  fc004500-fc004507 : serial

David



From david-b at pacbell.net  Thu Feb 15 21:56:38 2007
From: david-b at pacbell.net (David Brownell)
Date: Thu, 15 Feb 2007 18:56:38 -0800
Subject: [patch 2.6.20-git] at91_cf, fix build breakage and shrink codespace
Message-ID: <200702151856.38475.david-b@pacbell.net>

This is a minor correctness fix:  since the at91_cf driver probe() routine
is in the init section, it should use platform_driver_probe() instead of
leaving that pointer around in the driver struct after init section removal.

It also includes a major build breakage fix, which I'm guessing came from
incomplete code updates after removing "class_device" from this framework.

Signed-off-by: David Brownell <dbrownell at users.sourceforge.net>

Index: at91/drivers/pcmcia/at91_cf.c
===================================================================
--- at91.orig/drivers/pcmcia/at91_cf.c	2007-02-15 18:20:53.000000000 -0800
+++ at91/drivers/pcmcia/at91_cf.c	2007-02-15 18:31:27.000000000 -0800
@@ -277,7 +277,7 @@ static int __init at91_cf_probe(struct p
 		board->det_pin, board->irq_pin);
 
 	cf->socket.owner = THIS_MODULE;
-	cf->socket.dev.dev = &pdev->dev;
+	cf->socket.dev.parent = &pdev->dev;
 	cf->socket.ops = &at91_cf_ops;
 	cf->socket.resource_ops = &pccard_static_ops;
 	cf->socket.features = SS_CAP_PCCARD | SS_CAP_STATIC_MAP
@@ -360,7 +360,6 @@ static struct platform_driver at91_cf_dr
 		.name		= (char *) driver_name,
 		.owner		= THIS_MODULE,
 	},
-	.probe		= at91_cf_probe,
 	.remove		= __exit_p(at91_cf_remove),
 	.suspend	= at91_cf_suspend,
 	.resume		= at91_cf_resume,
@@ -370,7 +369,7 @@ static struct platform_driver at91_cf_dr
 
 static int __init at91_cf_init(void)
 {
-	return platform_driver_register(&at91_cf_driver);
+	return platform_driver_probe(&at91_cf_driver, at91_cf_probe);
 }
 module_init(at91_cf_init);
 


From wbc_company1 at yahoo.co.uk  Thu Feb 15 21:23:45 2007
From: wbc_company1 at yahoo.co.uk (W.B.C INCOPORATED)
Date: Fri, 16 Feb 2007 03:23:45 +0100 (CET)
Subject: VACANY ATTENTION NEEDED!!
Message-ID: <20070216022345.9379766F79C@web-streaming.net>



W.B.C INCOPORATED

UNION HOUSE,

ISLES OF MAN, 7M9 1DF,

BRITISH ISLE,

UNITED KINGDOM.

OUR REF: WBC/2028/E262/05,

DATE: 15-2-2007.

 

 

                               REQUEST FOR COMPANY REPRESENTATIVE

 

   I am Mr. Klaus Mueller,CEO and Owner of WBC Company based in the UK. 

WBC is a pan-European distributor specializing in semiconductors, providing 

customers with products and technical support for 16 leading manufacturers. 

Established in 1998 with headquarters in Poing, near Munich, WBC combines the 

strength and services of a technical consultant with basic distribution 

services.

 

WBC's Mission is to enhance Demand Creation and Knowledge Marketing to a point 

where WBC inspires new ideas and innovation for our customers. We strive to 

tur n knowledge into value for the benefit of our customers, our suppliers and 

our staff.



     Being a General Merchantile Company we are searching for representatives 

who can help us establish a medium of getting to our customers in the 

Canada/America,and some part of Europe as well as making payments through you 

to us.You do not have to leave your present job for this one because this job 

offer will be on a part time basis as it comes once in a while and 

remuneration is on a percentage basis of 10% of the total amount you receive 

from my customers at any time on my behalf.

 

     The reason why i seek assistance is that American and some parts of 

Europe check takes a long time to clear in the UK.thereby holding business 

down for me and my associates.I already have customers who are ready to remit 

cash to my agents now thus my contacting you.If you are interested in 

transacting business with us,do consult  me with  the following informations. 

via E-mail:wbc_inc orporated110 at yahoo.co.uk

 

(1)Your full names: 

(2)Contact address:

(3)Country: 

(4)Home/office phone: 

(5)Occupation: 

(6)Age: 

(7)sex:

 

Very respectfully,

Klaus Mueller

C.E.O,WBC Inc.

Email:wbc_company1 at yahoo.co.uk 






From damm at opensource.se  Sun Feb 18 03:49:30 2007
From: damm at opensource.se (Magnus Damm)
Date: Sun, 18 Feb 2007 17:49:30 +0900
Subject: [PATCH] ide-cs: Update device table
Message-ID: <20070218084930.31156.80938.sendpatchset@va-lsv.local.valinux.co.jp>

ide-cs: Update device table

Add CFA devices from I-O Data, Mitsubishi and Viking. Add SanDisk comment.

Signed-off-by: Magnus Damm <damm at opensource.se>
---

 Applies to 2.6.20-git14.

 ide-cs.c |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

--- 0002/drivers/ide/legacy/ide-cs.c
+++ work/drivers/ide/legacy/ide-cs.c	2007-02-18 16:25:32.000000000 +0900
@@ -359,14 +359,17 @@ void ide_release(struct pcmcia_device *l
 static struct pcmcia_device_id ide_ids[] = {
 	PCMCIA_DEVICE_FUNC_ID(4),
 	PCMCIA_DEVICE_MANF_CARD(0x0007, 0x0000),	/* Hitachi */
+	PCMCIA_DEVICE_MANF_CARD(0x000a, 0x0000),	/* I-O Data CFA */
+	PCMCIA_DEVICE_MANF_CARD(0x001c, 0x0001),	/* Mitsubishi CFA */
 	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x0704),
-	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),
+	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),	/* SanDisk CFA */
 	PCMCIA_DEVICE_MANF_CARD(0x0098, 0x0000),	/* Toshiba */
 	PCMCIA_DEVICE_MANF_CARD(0x00a4, 0x002d),
 	PCMCIA_DEVICE_MANF_CARD(0x00ce, 0x0000),	/* Samsung */
  	PCMCIA_DEVICE_MANF_CARD(0x0319, 0x0000),	/* Hitachi */
 	PCMCIA_DEVICE_MANF_CARD(0x2080, 0x0001),
-	PCMCIA_DEVICE_MANF_CARD(0x4e01, 0x0200),	/* Lexar */
+	PCMCIA_DEVICE_MANF_CARD(0x4e01, 0x0100),	/* Viking CFA */
+	PCMCIA_DEVICE_MANF_CARD(0x4e01, 0x0200),	/* Lexar, Viking CFA */
 	PCMCIA_DEVICE_PROD_ID123("Caravelle", "PSC-IDE ", "PSC000", 0x8c36137c, 0xd0693ab8, 0x2768a9f0),
 	PCMCIA_DEVICE_PROD_ID123("CDROM", "IDE", "MCD-601p", 0x1b9179ca, 0xede88951, 0x0d902f74),
 	PCMCIA_DEVICE_PROD_ID123("PCMCIA", "IDE CARD", "F1", 0x281f1c5d, 0x1907960c, 0xf7fde8b9),


From damm at opensource.se  Sun Feb 18 03:52:25 2007
From: damm at opensource.se (Magnus Damm)
Date: Sun, 18 Feb 2007 17:52:25 +0900
Subject: [PATCH] pata_pcmcia: Update device table
Message-ID: <20070218085225.447.95141.sendpatchset@va-lsv.local.valinux.co.jp>

pata_pcmcia: Update device table

Add CFA devices from I-O Data, Mitsubishi and Viking. Add SanDisk comment.

Signed-off-by: Magnus Damm <damm at opensource.se>
---

 Applies to 2.6.20-git14.

 pata_pcmcia.c |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

--- 0002/drivers/ata/pata_pcmcia.c
+++ work/drivers/ata/pata_pcmcia.c	2007-02-18 15:54:17.000000000 +0900
@@ -320,14 +320,17 @@ static void pcmcia_remove_one(struct pcm
 static struct pcmcia_device_id pcmcia_devices[] = {
 	PCMCIA_DEVICE_FUNC_ID(4),
 	PCMCIA_DEVICE_MANF_CARD(0x0007, 0x0000),	/* Hitachi */
+	PCMCIA_DEVICE_MANF_CARD(0x000a, 0x0000),	/* I-O Data CFA */
+	PCMCIA_DEVICE_MANF_CARD(0x001c, 0x0001),	/* Mitsubishi CFA */
 	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x0704),
-	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),
+	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),	/* SanDisk CFA */
 	PCMCIA_DEVICE_MANF_CARD(0x0098, 0x0000),	/* Toshiba */
 	PCMCIA_DEVICE_MANF_CARD(0x00a4, 0x002d),
 	PCMCIA_DEVICE_MANF_CARD(0x00ce, 0x0000),	/* Samsung */
  	PCMCIA_DEVICE_MANF_CARD(0x0319, 0x0000),	/* Hitachi */
 	PCMCIA_DEVICE_MANF_CARD(0x2080, 0x0001),
-	PCMCIA_DEVICE_MANF_CARD(0x4e01, 0x0200),	/* Lexar */
+	PCMCIA_DEVICE_MANF_CARD(0x4e01, 0x0100),	/* Viking CFA */
+	PCMCIA_DEVICE_MANF_CARD(0x4e01, 0x0200),	/* Lexar, Viking CFA */
 	PCMCIA_DEVICE_PROD_ID123("Caravelle", "PSC-IDE ", "PSC000", 0x8c36137c, 0xd0693ab8, 0x2768a9f0),
 	PCMCIA_DEVICE_PROD_ID123("CDROM", "IDE", "MCD-601p", 0x1b9179ca, 0xede88951, 0x0d902f74),
 	PCMCIA_DEVICE_PROD_ID123("PCMCIA", "IDE CARD", "F1", 0x281f1c5d, 0x1907960c, 0xf7fde8b9),


From bugme-daemon at bugzilla.kernel.org  Mon Feb 19 06:06:21 2007
From: bugme-daemon at bugzilla.kernel.org (bugme-daemon at bugzilla.kernel.org)
Date: Mon, 19 Feb 2007 03:06:21 -0800
Subject: [Bug 7384] Error allocating mem resources [CardBus]
Message-ID: <200702191106.l1JB6Lok022579@fire-2.osdl.org>

http://bugzilla.kernel.org/show_bug.cgi?id=7384

Markus.Rechberger at amd.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Owner|linux-                      |Markus.Rechberger at amd.com
                   |pcmcia at lists.infradead.org  |
             Status|NEW                         |ASSIGNED



------- Additional Comments From Markus.Rechberger at amd.com  2007-02-19 03:06 -------
Can you retry with the latest kernel? 
http://lkml.org/lkml/2006/12/18/266 that issue has been solved a while ago.


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


From dlclark at chtech.com  Mon Feb 19 12:22:42 2007
From: dlclark at chtech.com (David Clark)
Date: Mon, 19 Feb 2007 11:22:42 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070215182907.GA26928@isilmar.linta.de>
Message-ID: <004401c7544a$91577710$0f01a8c0@longhorn>

I have further traced what is happening in the kernel when it does a
memory probe.

"cs: memory probe 0x80000000-0xfcffffff"
"	excluding 0x80000000-0xfcffffff"

As is steps through the memory between 0x80000000 and 0xfcffffff is does
find several regions that it can successfully claim.  Once it claims a
region, it then attempts to validate the CIS (pccard_validate_cis())
using that memory region however it fails to do so.  It simply cannot
read the CIS.  I don't completely understand how the memory mapping to
the CIS is supposed to work.  Is the card or socket controller supposed
to be setup to allow this access?

The socket controller is setup with memory windows of
0x80000000-0x803ff000 and 0xbf8ff000-0xbfcfe000.  As the kernel probes
memory, it finds that 0x80000000=0x803ff000 is not available.  It finds
that 0x80800000 (searches using a step size of 0x00800000) is available
and attempts to access the CIS at the location.  This outside of the
socket controller's memory windows so is it supposed to be able to
access the CIS in this memory range?  This continues through the entire
probed memory range.  Whenever it hits a memory location that part of
the allocated memory window or allocated to another PCI device, it finds
that the resource is not available.  When it hit a free memory range, it
cannot access the CIS and fails to validate.  What am I missing?

David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark at chtech.com
 




From bzolnier at gmail.com  Mon Feb 19 18:04:06 2007
From: bzolnier at gmail.com (Bartlomiej Zolnierkiewicz)
Date: Tue, 20 Feb 2007 00:04:06 +0100
Subject: [PATCH] ide-cs: Update device table
In-Reply-To: <20070218084930.31156.80938.sendpatchset@va-lsv.local.valinux.co.jp>
References: <20070218084930.31156.80938.sendpatchset@va-lsv.local.valinux.co.jp>
Message-ID: <200702200004.06881.bzolnier@gmail.com>


On Sunday 18 February 2007 09:49, Magnus Damm wrote:
> ide-cs: Update device table
> 
> Add CFA devices from I-O Data, Mitsubishi and Viking. Add SanDisk comment.
> 
> Signed-off-by: Magnus Damm <damm at opensource.se>

applied, thanks


From anders.bogild at gmail.com  Mon Feb 19 18:50:44 2007
From: anders.bogild at gmail.com (AndersB)
Date: Tue, 20 Feb 2007 00:50:44 +0100
Subject: yenta_socket broken on Acer Travelmate 505 series
Message-ID: <45DA37D4.6040905@gmail.com>

Hi
I havnt been able to use my D-Link DUB-C2 usb 2.0 pcmcia card on my Acer 
Travelmate 506t since kernel 2.6.12 and i have finally tracked down the 
error to the message "Yenta O2: old bridge, disabling read 
prefetch/write burst" apearing in dmesg.

I removed the case for the O2_6812 and everything works for me now.

Here is the patch:

*** drivers/pcmcia/o2micro.h    Tue Feb 20 00:26:05 2007
--- ../linux-2.6.19-gentoo-r5-acer_tm505/drivers/pcmcia/o2micro.h       
Tue Feb 20 00:26:30 2007
***************
*** 133,173 ****
         * working. for some bridges it is at 0x94, for others at 0xD4. it's
         * ok to write to both registers on all O2 bridges.
         * from Eric Still, 02Micro.
         */
        u8 a, b;

        if (PCI_FUNC(socket->dev->devfn) == 0) {
                a = config_readb(socket, O2_RESERVED1);
                b = config_readb(socket, O2_RESERVED2);

                printk(KERN_INFO "Yenta O2: res at 0x94/0xD4: 
%02x/%02x\n", a, b);

                switch (socket->dev->device) {
                /*
                 * older bridges have problems with both read prefetch 
and write
                 * bursting depending on the combination of the chipset, 
bridge
                 * and the cardbus card. so disable them to be on the 
safe side.
                 */
                case PCI_DEVICE_ID_O2_6729:
                case PCI_DEVICE_ID_O2_6730:
-               case PCI_DEVICE_ID_O2_6812:
                case PCI_DEVICE_ID_O2_6832:
                case PCI_DEVICE_ID_O2_6836:
                        printk(KERN_INFO "Yenta O2: old bridge, 
disabling read prefetch/write burst\n");
                        config_writeb(socket, O2_RESERVED1,
                                      a & ~(O2_RES_READ_PREFETCH | 
O2_RES_WRITE_BURST));
                        config_writeb(socket, O2_RESERVED2,
                                      b & ~(O2_RES_READ_PREFETCH | 
O2_RES_WRITE_BURST));
                        break;

                default:
                        printk(KERN_INFO "Yenta O2: enabling read 
prefetch/write burst\n");
                        config_writeb(socket, O2_RESERVED1,
                                      a | O2_RES_READ_PREFETCH | 
O2_RES_WRITE_BURST);
                        config_writeb(socket, O2_RESERVED2,
                                      b | O2_RES_READ_PREFETCH | 
O2_RES_WRITE_BURST);
                }
        }

        return 0;
  }
--- 133,172 ----

Before the patch lspci gives

00:06.0 CardBus bridge: O2 Micro, Inc. OZ6812 CardBus Controller (rev 05)
        Subsystem: Acer Incorporated [ALI] Unknown device 100b
        Flags: bus master, stepping, slow devsel, latency 168, IRQ 11
        Memory at 14000000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=00, secondary=01, subordinate=04, sec-latency=176
        Memory window 0: 10000000-11fff000 (prefetchable)
        Memory window 1: 12000000-13fff000
        I/O window 0: 00001800-000018ff
        I/O window 1: 00001c00-00001cff
        16-bit legacy interface ports at 0001

01:00.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
        Subsystem: D-Link System Inc Unknown device 0035
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at 12000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

01:00.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
        Subsystem: D-Link System Inc Unknown device 0035
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at 12001000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

01:00.2 USB Controller: NEC Corporation USB 2.0 (rev 02) (prog-if 20 [EHCI])
        Subsystem: D-Link System Inc Unknown device f100
        Flags: bus master, medium devsel, latency 68, IRQ 11
        Memory at 12002000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2



_after_ the patch things work, but there is some funky stuff happening 
with info for the pcmcia card (the last lines):

00:06.0 CardBus bridge: O2 Micro, Inc. OZ6812 CardBus Controller (rev 05)
        Subsystem: Acer Incorporated [ALI] Unknown device 100b
        Flags: bus master, stepping, slow devsel, latency 168, IRQ 11
        Memory at 14000000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=00, secondary=01, subordinate=04, sec-latency=176
        Memory window 0: 10000000-11fff000 (prefetchable)
        Memory window 1: 12000000-13fff000
        I/O window 0: 00001800-000018ff
        I/O window 1: 00001c00-00001cff
        16-bit legacy interface ports at 0001

01:00.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
        Subsystem: D-Link System Inc Unknown device 0035
        Flags: bus master, VGA palette snoop, stepping, fast Back2Back, 
66MHz, user-definable features, ?? devsel, latency 8, IRQ 11
        Memory at 12000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

01:00.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
        Subsystem: D-Link System Inc Unknown device 0035
        Flags: medium devsel, IRQ 11
        Memory at 12001000 (32-bit, non-prefetchable) [disabled] [size=4K]
        Capabilities: [40] Power Management version 2

01:00.2 Class ffff: Illegal Vendor ID Unknown device ffff (rev ff) 
(prog-if ff)
        Subsystem: D-Link System Inc Unknown device f100
        Flags: bus master, medium devsel, latency 68, IRQ 11
        Memory at 12002000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2

Should i just ignore this ?

Cheers!
    Anders B


From geda.mail at gmail.com  Tue Feb 20 01:15:01 2007
From: geda.mail at gmail.com (primorec)
Date: Mon, 19 Feb 2007 22:15:01 -0800
Subject: NI GPIB PCMCIA not recognized (AGAIN)
Message-ID: <a9cba75b0702192215w21c46a46s1fb0469f0fe7c88e@mail.gmail.com>

Sorry folks, I've pressed __send__ button too early in the previous posting

HI All,

It does not matter what I do, the kernel (or OS ?) does not recognize
a standard NI GPIB PCMCIA card.

hardware:
IBM ThinkPad T22
RAM 384MB
00:02.0 CardBus bridge: Texas Instruments PC1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PC1450 (rev 03)
OS: Fedora Core 6 (kernel 2.6.18-1.2798.fc6xen
       CentOS 4.4 (kernel 2.6.9-34.EL)
       CentOS 4.4 (kernel 2.6.18.6)
       CentOS 4.4 (kernel 2.6.19.3)
       CentOS 4.4 (kernel 2.6.9-42.EL)

I've tried all the options from above. On all CentOS versions the
card is recognised a 'Anonymous Memory"  and the pcmcia subsystem
tries to load the memory_cs.

Log files slightly differ...  but more or less I get  the following output

Feb 19 09:02:32 localhost kernel: pccard: PCMCIA card inserted into slot 0
Feb 19 09:02:32 localhost kernel: cs: memory probe
0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
Feb 19 09:02:32 localhost kernel: cs: memory probe
0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
Feb 19 09:02:32 localhost kernel: cs: warning: no high memory space available!
Feb 19 09:02:32 localhost kernel: cs: warning: no high memory space available!
Feb 19 09:02:32 localhost cardmgr[2589]: socket 0: Anonymous Memory
Feb 19 09:02:32 localhost kernel: 2.6. kernels use pcmciamtd instead
of memory_cs.c and do not require special
Feb 19 09:02:32 localhost kernel: MTD handling any more.
Feb 19 09:02:32 localhost cardmgr[2589]: executing: 'modprobe memory_cs 2>&1'
Feb 19 09:02:32 localhost cardmgr[2589]: + FATAL: Module memory_cs not found.
Feb 19 09:02:32 localhost cardmgr[2589]: modprobe exited with status 1
Feb 19 09:02:32 localhost cardmgr[2589]: module
/lib/modules/2.6.18.6-default _3/pcmcia/memory_cs.o not available
Feb 19 09:02:32 localhost cardmgr[2589]: bind 'memory_cs' to socket 0
failed: Invalid argument

The Fedora Core 6 is different.  It does not complain about
'memory_cs". At the end, the result is the same.
The NI GPIB card is not recognized.

The 'pccardctl ident'  (cardctl ident)  brings __nothing__ back.
Socket 0:
  no product info available

pccardctl status  (cardctl status)
Socket 0:
  5V 16-bit PC Card

------------------------------------------------------------------------
however, when I do the same tests on ThinkPad T43, results are different
------------------------------------------------------------------------
hardware:
IBM ThinkPad T43
RAM 1GB
04:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
OS: CentOS 4.4 (kernel 2.6.9-34.EL)

cardctl ident
Socket 0:
  product info: "National Instruments", "PCMCIA-GPIB", "Rev. C", ""
  manfid: 0x010b, 0x4882

  cardctl status
Socket 0:
  5V 16-bit PC Card
  function 0: [busy]

What I am doing wrong ?
 Any hint | advice | solution | explanation | help  is more than welcome

Regards

Igor


From jeff at garzik.org  Tue Feb 20 11:04:47 2007
From: jeff at garzik.org (Jeff Garzik)
Date: Tue, 20 Feb 2007 11:04:47 -0500
Subject: [PATCH] pata_pcmcia: Update device table
In-Reply-To: <20070218085225.447.95141.sendpatchset@va-lsv.local.valinux.co.jp>
References: <20070218085225.447.95141.sendpatchset@va-lsv.local.valinux.co.jp>
Message-ID: <45DB1C1F.3060504@garzik.org>

Magnus Damm wrote:
> pata_pcmcia: Update device table
> 
> Add CFA devices from I-O Data, Mitsubishi and Viking. Add SanDisk comment.
> 
> Signed-off-by: Magnus Damm <damm at opensource.se>
> ---
> 
>  Applies to 2.6.20-git14.

applied




From mano at roarinelk.homelinux.net  Wed Feb 21 08:47:20 2007
From: mano at roarinelk.homelinux.net (Manuel Lauss)
Date: Wed, 21 Feb 2007 14:47:20 +0100
Subject: [PATCH] 2.6.21-rc1: more fallout from class_device changes
Message-ID: <20070221134720.GA10407@roarinelk.homelinux.net>

More fallout from the PCMCIA class_device changes.

The first hunk is run-tested on SH-4, the others are converted
in the spirit of the original conversion.


Signed-off-by: Manuel Lauss  <mano at roarinelk.homelinux.net>


--- linux-2.6.21-rc1/drivers/pcmcia/rsrc_mgr.c	2007-02-21 09:24:00.549482000 +0100
+++ linux-2.6.21-rc1-work/drivers/pcmcia/rsrc_mgr.c	2007-02-21 10:40:18.789482000 +0100
@@ -232,7 +232,7 @@ static struct resource *iodyn_find_io_re
 		unsigned long align, struct pcmcia_socket *s)
 {
 	struct resource *res = make_resource(0, num, IORESOURCE_IO,
-					     s->dev.class_id);
+					     s->dev.bus_id);
 	struct pcmcia_align_data data;
 	unsigned long min = base;
 	int ret;
--- linux-2.6.21-rc1/drivers/pcmcia/hd64465_ss.c	2007-02-21 09:24:00.499482000 +0100
+++ linux-2.6.21-rc1-work/drivers/pcmcia/hd64465_ss.c	2007-02-21 10:43:05.999482000 +0100
@@ -907,7 +907,7 @@ static int __init init_hs(void)
 
 	for (i=0; i<HS_MAX_SOCKETS; i++) {
 		unsigned int ret;
-		hs_sockets[i].socket.dev.dev = &hd64465_device.dev;		
+		hs_sockets[i].socket.dev.parent = &hd64465_device.dev;		
 		hs_sockets[i].number = i;
 		ret = pcmcia_register_socket(&hs_sockets[i].socket);
 		if (ret && i)
--- linux-2.6.21-rc1/drivers/pcmcia/m32r_cfc.c	2007-02-21 09:24:00.499482000 +0100
+++ linux-2.6.21-rc1-work/drivers/pcmcia/m32r_cfc.c	2007-02-21 10:48:18.409482000 +0100
@@ -760,7 +760,7 @@ static int __init init_m32r_pcc(void)
 	/* Set up interrupt handler(s) */
 
 	for (i = 0 ; i < pcc_sockets ; i++) {
-		socket[i].socket.dev.dev = &pcc_device.dev;
+		socket[i].socket.dev.parent = &pcc_device.dev;
 		socket[i].socket.ops = &pcc_operations;
 		socket[i].socket.resource_ops = &pccard_nonstatic_ops;
 		socket[i].socket.owner = THIS_MODULE;
--- linux-2.6.21-rc1/drivers/pcmcia/m8xx_pcmcia.c	2007-02-21 09:24:00.519482000 +0100
+++ linux-2.6.21-rc1-work/drivers/pcmcia/m8xx_pcmcia.c	2007-02-21 10:49:03.249482000 +0100
@@ -1321,7 +1321,7 @@ static int __init m8xx_init(void)
 		socket[i].socket.ops = &m8xx_services;
 		socket[i].socket.resource_ops = &pccard_iodyn_ops;
 		socket[i].socket.cb_dev = NULL;
-		socket[i].socket.dev.dev = &m8xx_device.dev;
+		socket[i].socket.dev.parent = &m8xx_device.dev;
 	}
 
 	for (i = 0; i < PCMCIA_SOCKETS_NO; i++)
--- linux-2.6.21-rc1/drivers/pcmcia/omap_cf.c	2007-02-21 09:24:00.519482000 +0100
+++ linux-2.6.21-rc1-work/drivers/pcmcia/omap_cf.c	2007-02-21 10:49:12.289482000 +0100
@@ -291,7 +291,7 @@ static int __devinit omap_cf_probe(struc
 		omap_cf_present() ? "present" : "(not present)");
 
 	cf->socket.owner = THIS_MODULE;
-	cf->socket.dev.dev = dev;
+	cf->socket.dev.parent = dev;
 	cf->socket.ops = &omap_cf_ops;
 	cf->socket.resource_ops = &pccard_static_ops;
 	cf->socket.features = SS_CAP_PCCARD | SS_CAP_STATIC_MAP
--- linux-2.6.21-rc1/drivers/pcmcia/vrc4171_card.c	2007-02-21 09:24:00.589482000 +0100
+++ linux-2.6.21-rc1-work/drivers/pcmcia/vrc4171_card.c	2007-02-21 10:49:25.609482000 +0100
@@ -596,7 +596,7 @@ static int __devinit vrc4171_add_sockets
 		}
 
 		sprintf(socket->name, "NEC VRC4171 Card Slot %1c", 'A' + slot);
-		socket->pcmcia_socket.dev.dev = &vrc4171_card_device.dev;
+		socket->pcmcia_socket.dev.parent = &vrc4171_card_device.dev;
 		socket->pcmcia_socket.ops = &vrc4171_pccard_operations;
 		socket->pcmcia_socket.owner = THIS_MODULE;
 


From markus.rechberger at amd.com  Wed Feb 21 09:18:48 2007
From: markus.rechberger at amd.com (Markus Rechberger)
Date: Wed, 21 Feb 2007 15:18:48 +0100
Subject: [PATCH] pcmcia/pccard deadlock fix
Message-ID: <45DC54C8.2020301@amd.com>

following patch prevents a mutex/semaphore deadlock within the pcmcia
framework when ejecting devices multiple times using pccardctl eject.

For some more details see:
http://lkml.org/lkml/2007/2/19/58

Signed-off-by: Markus Rechberger <markus.rechberger at amd.com>

-- 
Markus Rechberger
Operating System Research Center
AMD Saxony LLC & Co. KG

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pcmcia-pccard-deadlock-fix.diff
Url: http://lists.infradead.org/pipermail/linux-pcmcia/attachments/20070221/84dc0017/attachment.pl 

From alan at lxorguk.ukuu.org.uk  Wed Feb 21 10:38:07 2007
From: alan at lxorguk.ukuu.org.uk (Alan)
Date: Wed, 21 Feb 2007 15:38:07 +0000
Subject: [PATCH] pata_pcmcia: Update device table
In-Reply-To: <20070218085225.447.95141.sendpatchset@va-lsv.local.valinux.co.jp>
References: <20070218085225.447.95141.sendpatchset@va-lsv.local.valinux.co.jp>
Message-ID: <20070221153807.71e34cde@lxorguk.ukuu.org.uk>

On Sun, 18 Feb 2007 17:52:25 +0900
Magnus Damm <damm at opensource.se> wrote:

> pata_pcmcia: Update device table
> 
> Add CFA devices from I-O Data, Mitsubishi and Viking. Add SanDisk comment.
> 
> Signed-off-by: Magnus Damm <damm at opensource.se>

Acked-by: Alan Cox <alan at redhat.com>


From drawab at cyber.net.pk  Thu Feb 22 04:07:21 2007
From: drawab at cyber.net.pk (Dr. Awab Alvi)
Date: Thu, 22 Feb 2007 14:07:21 +0500
Subject: Linksys WPC11 v3
Message-ID: <200702221407.21532.drawab@cyber.net.pk>

Hi,

Just from a few days I have been having strange problems with my PCMCIA 
Linksys WPC11 v3.  Everything was apparently fine until suddenly out of the
blue the PCMCIA card stopped working. I have tried repeatedly by unpluging
and replugin the item with no results.  The lights on the card shine for a
brief 3 seconds and disappear as if dead.  I have tested the card on the
alternate windows installation on the same machine where it works fine. 
Seems to be a UBUNTU EDGY problem.

I have even used another PCMCIA Wifi Card - Microsoft MN-520 with the exact 
same results lights that disappear. Even tired it on the other PCMCIA slot
with the same result -  'dmesg' command shows

cs: pcmcia_socket1: time out after reset

A few days prior to the problem I did see a strange message of the Card
Utility being deprecated - but paid little attention to the exact message
since the PCMCIA card was working fine

I am using UBUNTU EDGY on Toshiba Satellite P20-S103

Thank you for listening

-------------------------------------------------------


From gregkh at suse.de  Thu Feb 22 15:35:07 2007
From: gregkh at suse.de (gregkh at suse.de)
Date: Thu, 22 Feb 2007 12:35:07 -0800
Subject: patch
	driver-core-more-fallout-from-class_device-changes-for-pcmcia.patch
	added to gregkh-2.6 tree
In-Reply-To: <20070221134720.GA10407@roarinelk.homelinux.net>
Message-ID: <20070222203633.224E1C20DBE@imap.suse.de>


This is a note to let you know that I've just added the patch titled

     Subject: Driver core: more fallout from class_device changes for pcmcia

to my gregkh-2.6 tree.  Its filename is

     driver-core-more-fallout-from-class_device-changes-for-pcmcia.patch

This tree can be found at 
    http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/


>From mano at roarinelk.homelinux.net Wed Feb 21 05:47:27 2007
From: Manuel Lauss <mano at roarinelk.homelinux.net>
Date: Wed, 21 Feb 2007 14:47:20 +0100
Subject: Driver core: more fallout from class_device changes for pcmcia
To: <linux-pcmcia at lists.infradead.org>
Cc: gregkh at suse.de
Message-ID: <20070221134720.GA10407 at roarinelk.homelinux.net>
Content-Disposition: inline


More fallout from the PCMCIA class_device changes.

The first hunk is run-tested on SH-4, the others are converted
in the spirit of the original conversion.


Signed-off-by: Manuel Lauss  <mano at roarinelk.homelinux.net>
Signed-off-by: Greg Kroah-Hartman <gregkh at suse.de>


---
 drivers/pcmcia/hd64465_ss.c   |    2 +-
 drivers/pcmcia/m32r_cfc.c     |    2 +-
 drivers/pcmcia/m8xx_pcmcia.c  |    2 +-
 drivers/pcmcia/omap_cf.c      |    2 +-
 drivers/pcmcia/rsrc_mgr.c     |    2 +-
 drivers/pcmcia/vrc4171_card.c |    2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

--- gregkh-2.6.orig/drivers/pcmcia/hd64465_ss.c
+++ gregkh-2.6/drivers/pcmcia/hd64465_ss.c
@@ -907,7 +907,7 @@ static int __init init_hs(void)
 
 	for (i=0; i<HS_MAX_SOCKETS; i++) {
 		unsigned int ret;
-		hs_sockets[i].socket.dev.dev = &hd64465_device.dev;		
+		hs_sockets[i].socket.dev.parent = &hd64465_device.dev;
 		hs_sockets[i].number = i;
 		ret = pcmcia_register_socket(&hs_sockets[i].socket);
 		if (ret && i)
--- gregkh-2.6.orig/drivers/pcmcia/m32r_cfc.c
+++ gregkh-2.6/drivers/pcmcia/m32r_cfc.c
@@ -760,7 +760,7 @@ static int __init init_m32r_pcc(void)
 	/* Set up interrupt handler(s) */
 
 	for (i = 0 ; i < pcc_sockets ; i++) {
-		socket[i].socket.dev.dev = &pcc_device.dev;
+		socket[i].socket.dev.parent = &pcc_device.dev;
 		socket[i].socket.ops = &pcc_operations;
 		socket[i].socket.resource_ops = &pccard_nonstatic_ops;
 		socket[i].socket.owner = THIS_MODULE;
--- gregkh-2.6.orig/drivers/pcmcia/m8xx_pcmcia.c
+++ gregkh-2.6/drivers/pcmcia/m8xx_pcmcia.c
@@ -1321,7 +1321,7 @@ static int __init m8xx_init(void)
 		socket[i].socket.ops = &m8xx_services;
 		socket[i].socket.resource_ops = &pccard_iodyn_ops;
 		socket[i].socket.cb_dev = NULL;
-		socket[i].socket.dev.dev = &m8xx_device.dev;
+		socket[i].socket.dev.parent = &m8xx_device.dev;
 	}
 
 	for (i = 0; i < PCMCIA_SOCKETS_NO; i++)
--- gregkh-2.6.orig/drivers/pcmcia/omap_cf.c
+++ gregkh-2.6/drivers/pcmcia/omap_cf.c
@@ -291,7 +291,7 @@ static int __devinit omap_cf_probe(struc
 		omap_cf_present() ? "present" : "(not present)");
 
 	cf->socket.owner = THIS_MODULE;
-	cf->socket.dev.dev = dev;
+	cf->socket.dev.parent = dev;
 	cf->socket.ops = &omap_cf_ops;
 	cf->socket.resource_ops = &pccard_static_ops;
 	cf->socket.features = SS_CAP_PCCARD | SS_CAP_STATIC_MAP
--- gregkh-2.6.orig/drivers/pcmcia/rsrc_mgr.c
+++ gregkh-2.6/drivers/pcmcia/rsrc_mgr.c
@@ -232,7 +232,7 @@ static struct resource *iodyn_find_io_re
 		unsigned long align, struct pcmcia_socket *s)
 {
 	struct resource *res = make_resource(0, num, IORESOURCE_IO,
-					     s->dev.class_id);
+					     s->dev.bus_id);
 	struct pcmcia_align_data data;
 	unsigned long min = base;
 	int ret;
--- gregkh-2.6.orig/drivers/pcmcia/vrc4171_card.c
+++ gregkh-2.6/drivers/pcmcia/vrc4171_card.c
@@ -596,7 +596,7 @@ static int __devinit vrc4171_add_sockets
 		}
 
 		sprintf(socket->name, "NEC VRC4171 Card Slot %1c", 'A' + slot);
-		socket->pcmcia_socket.dev.dev = &vrc4171_card_device.dev;
+		socket->pcmcia_socket.dev.parent = &vrc4171_card_device.dev;
 		socket->pcmcia_socket.ops = &vrc4171_pccard_operations;
 		socket->pcmcia_socket.owner = THIS_MODULE;
 


Patches currently in gregkh-2.6 which might be from mano at roarinelk.homelinux.net are



From info_agent at yahoo.co.uk  Fri Feb 23 21:56:57 2007
From: info_agent at yahoo.co.uk (notification)
Date: Sat, 24 Feb 2007 03:56:57 +0100 (CET)
Subject: winning notification..........contcat    claims agent               
Message-ID: <20070224025657.ACBEF3C55B1@ema-hosting.de>



NATIONAL LOTTERY

PROMOTIONS/ PRIZE AWARD DEPARTMENT.

79 BOVILL ROAD

LONDON. SE23 1EL.

>>>>>>>>>>>>>>>>>>>>>>

Ref: EGS/2251256003/02

Batch: 14/0017/1PD

>>>>>>>>>>>>>>>>>>>>>>



DATE: 22th february, 2007



                               WINNING NOTIFICATION

                       >>>>>>>>>>>>>>>>>>>>>>>>>>>>

Your email account have been picked as a winner of Six Hundred Thousand

Pounds Sterling (?600,000.00) in cash credited to file 

KTU/9023118308/03.

This is from a total sum of Four Million, Two hundred Thousand Pounds

Sterling (?4,200,000.00) shared amongst seven winners. This results is 

now

released to you on the 22th of february, 2007 and your email address

attached to ticket number: 56475600545 188 with Serial number

5368/02.participants were selected through a computer ballot system 

drawn

from Microsoft users from company and individual email address.



Anybody under the age of 17 and members of the affiliate agencies are

automatically not allowed to participate in this program.



1. Full name and address.

2. Country.

3. Tel and fax number.

4. Occupation.

6. Languages Spoken.

7. Age:



<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Foreign Service Manager

Mr. Adams Richards,

DIRECT TELEPHONE:     +44 701 421 9046

Fax:                             +44-871-715-6044

Email:claimsagent_00001 at yahoo.co.uk

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



Yours Sincerely,

Mrs.Ann Roberts,

Executive (International Sweepstakes).












From dmonakhov at openvz.org  Mon Feb 26 11:09:17 2007
From: dmonakhov at openvz.org (Monakhov Dmitriy)
Date: Mon, 26 Feb 2007 19:09:17 +0300
Subject: [PATCH 2/3] pcmcia: Handle request_irq() failure while opening device
Message-ID: <87zm70q4sy.fsf@sw.ru>



Signed-off-by: Monakhov Dmitriy <dmonakhov at openvz.org>
---
 drivers/net/pcmcia/axnet_cs.c |    8 +++++++-
 drivers/net/pcmcia/pcnet_cs.c |    8 +++++++-
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/drivers/net/pcmcia/axnet_cs.c b/drivers/net/pcmcia/axnet_cs.c
index 6139048..9b57bab 100644
--- a/drivers/net/pcmcia/axnet_cs.c
+++ b/drivers/net/pcmcia/axnet_cs.c
@@ -523,6 +523,7 @@ static int axnet_open(struct net_device *dev)
 {
     axnet_dev_t *info = PRIV(dev);
     struct pcmcia_device *link = info->p_dev;
+    int err = 0;
     
     DEBUG(2, "axnet_open('%s')\n", dev->name);
 
@@ -531,7 +532,12 @@ static int axnet_open(struct net_device *dev)
 
     link->open++;
 
-    request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
+    err = request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
+    if (err) {
+		printk("axnet_cs: request_irq() failed  %s\n", dev->name);
+		link->open--;
+		return -EBUSY;
+    }
 
     info->link_status = 0x00;
     init_timer(&info->watchdog);
diff --git a/drivers/net/pcmcia/pcnet_cs.c b/drivers/net/pcmcia/pcnet_cs.c
index d88e9b2..13923ea 100644
--- a/drivers/net/pcmcia/pcnet_cs.c
+++ b/drivers/net/pcmcia/pcnet_cs.c
@@ -962,6 +962,7 @@ static int pcnet_open(struct net_device *dev)
 {
     pcnet_dev_t *info = PRIV(dev);
     struct pcmcia_device *link = info->p_dev;
+    int err = 0;
 
     DEBUG(2, "pcnet_open('%s')\n", dev->name);
 
@@ -971,7 +972,12 @@ static int pcnet_open(struct net_device *dev)
     link->open++;
 
     set_misc_reg(dev);
-    request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, dev_info, dev);
+    err = request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, dev_info, dev);
+    if (err) {
+		printk("pcnet_open: request_irq() failed  %s\n", dev->name);
+		link->open--;
+		return -EBUSY;
+    }
 
     info->phy_id = info->eth_phy;
     info->link_status = 0x00;
-- 
1.5.0.1




From dmonakhov at openvz.org  Mon Feb 26 13:07:38 2007
From: dmonakhov at openvz.org (Dmitriy Monakhov)
Date: Mon, 26 Feb 2007 21:07:38 +0300
Subject: [PATCH 2/3] pcmcia: Handle request_irq() failure while opening
	device
In-Reply-To: <87zm70q4sy.fsf@sw.ru> (Monakhov Dmitriy's message of "Mon,
	26 Feb 2007 19:09:17 +0300")
References: <87zm70q4sy.fsf@sw.ru>
Message-ID: <87649oaj2t.fsf@sw.ru>

Monakhov Dmitriy <dmonakhov at openvz.org> writes:

> Signed-off-by: Monakhov Dmitriy <dmonakhov at openvz.org>
> ---
>  drivers/net/pcmcia/axnet_cs.c |    8 +++++++-
>  drivers/net/pcmcia/pcnet_cs.c |    8 +++++++-
>  2 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/pcmcia/axnet_cs.c b/drivers/net/pcmcia/axnet_cs.c
> index 6139048..9b57bab 100644
> --- a/drivers/net/pcmcia/axnet_cs.c
> +++ b/drivers/net/pcmcia/axnet_cs.c
> @@ -523,6 +523,7 @@ static int axnet_open(struct net_device *dev)
>  {
>      axnet_dev_t *info = PRIV(dev);
>      struct pcmcia_device *link = info->p_dev;
> +    int err = 0;
>      
>      DEBUG(2, "axnet_open('%s')\n", dev->name);
>  
> @@ -531,7 +532,12 @@ static int axnet_open(struct net_device *dev)
>  
>      link->open++;
>  
> -    request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
> +    err = request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
> +    if (err) {
> +		printk("axnet_cs: request_irq() failed  %s\n", dev->name);
> +		link->open--;
> +		return -EBUSY;
As David Miller noted it is better to return exact error code from request_irq(),
truly most net_device->open() functions return error code without changing.  
The updated patch version following:

Signed-off-by: Monakhov Dmitriy <dmonakhov at openvz.org>
---
 drivers/net/pcmcia/axnet_cs.c |    8 +++++++-
 drivers/net/pcmcia/pcnet_cs.c |    8 +++++++-
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/drivers/net/pcmcia/axnet_cs.c b/drivers/net/pcmcia/axnet_cs.c
index 6139048..9b57bab 100644
--- a/drivers/net/pcmcia/axnet_cs.c
+++ b/drivers/net/pcmcia/axnet_cs.c
@@ -523,6 +523,7 @@ static int axnet_open(struct net_device *dev)
 {
     axnet_dev_t *info = PRIV(dev);
     struct pcmcia_device *link = info->p_dev;
+    int err = 0;
     
     DEBUG(2, "axnet_open('%s')\n", dev->name);
 
@@ -531,7 +532,12 @@ static int axnet_open(struct net_device *dev)
 
     link->open++;
 
-    request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
+    err = request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
+    if (err) {
+		printk("axnet_cs: request_irq() failed  %s\n", dev->name);
+		link->open--;
+		return err;
+    }
 
     info->link_status = 0x00;
     init_timer(&info->watchdog);
diff --git a/drivers/net/pcmcia/pcnet_cs.c b/drivers/net/pcmcia/pcnet_cs.c
index d88e9b2..13923ea 100644
--- a/drivers/net/pcmcia/pcnet_cs.c
+++ b/drivers/net/pcmcia/pcnet_cs.c
@@ -962,6 +962,7 @@ static int pcnet_open(struct net_device *dev)
 {
     pcnet_dev_t *info = PRIV(dev);
     struct pcmcia_device *link = info->p_dev;
+    int err = 0;
 
     DEBUG(2, "pcnet_open('%s')\n", dev->name);
 
@@ -971,7 +972,12 @@ static int pcnet_open(struct net_device *dev)
     link->open++;
 
     set_misc_reg(dev);
-    request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, dev_info, dev);
+    err = request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, dev_info, dev);
+    if (err) {
+		printk("pcnet_open: request_irq() failed  %s\n", dev->name);
+		link->open--;
+		return err;
+    }
 
     info->phy_id = info->eth_phy;
     info->link_status = 0x00;
-- 
1.5.0.1



From milan.avramovic at snt.co.yu  Mon Feb 26 06:03:58 2007
From: milan.avramovic at snt.co.yu (Milan =?UTF-8?Q?Avramovi=C4=87?=)
Date: Mon, 26 Feb 2007 12:03:58 +0100
Subject: Card not detected
Message-ID: <1172487838.32502.6.camel@cmjlapwifi.lan>

I have a problem with a pcmcia card on a laptop. Cardbus driver is
detected (yenta_socket); however card is not detected on the bus.

Card is Omnikey CardMan 4009, smart card reader. 

Please give me any hints what should be done to make pcmcia see the
card. Manually loading cm4000_cs did not make it visible.

Here's lspci & lspcmcia otuput:

------ 8< ------ 8< ------ 8< ------ 8< ------ 

[root at cmjlapwifi ~]# lspcmcia -vvv
Socket 0 Bridge:        [yenta_cardbus]         (bus ID: 0000:04:06.0)
        Configuration:  state: on       ready: yes
                        Available IRQs: 3, 4, 5, 6, 7, 10, 11
                        Available ioports:      0x00000100 - 0x00000377
                                                0x00000380 - 0x000003af
                                                0x000003e0 - 0x000004ff
                                                0x00000820 - 0x000008ff
                                                0x00000a00 - 0x00000aff
                                                0x00000c00 - 0x00000cf7
                                                0x00007000 - 0x00007fff
                        Available iomem:        0x000c0000 - 0x000fffff
                                                0x40000000 - 0x43ffffff
                                                0x60000000 - 0x60ffffff
                                                0xa0000000 - 0xa0ffffff
                                                0xe8100000 - 0xe83fffff
[root at cmjlapwifi ~]# lspci -v
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and
945GT Express Memory Controller Hub (rev 03)
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller: Intel Corporation Mobile
945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
(prog-if 00 [VGA])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e8400000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at 6000 [size=8]
        Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Memory at e8480000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [90] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable-
        Capabilities: [d0] Power Management version 2

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML
Express Integrated Graphics Controller (rev 03)
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, fast devsel, latency 0
        Memory at e8500000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 2

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 01)
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, fast devsel, latency 0, IRQ 21
        Memory at e8580000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
        Capabilities: [70] Express Unknown type IRQ 0

00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 1 (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: e8000000-e80fffff
        Capabilities: [40] Express Root Port (Slot+) IRQ 0
        Capabilities: [80] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable-
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2

00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 3 (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: 00004000-00005fff
        Memory behind bridge: e4000000-e7ffffff
        Capabilities: [40] Express Root Port (Slot+) IRQ 0
        Capabilities: [80] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable-
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2

00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 4 (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        I/O behind bridge: 00002000-00003fff
        Memory behind bridge: e0000000-e3ffffff
        Capabilities: [40] Express Root Port (Slot+) IRQ 0
        Capabilities: [80] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable-
        Capabilities: [90] #0d [0000]
        Capabilities: [a0] Power Management version 2

00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
#1 (rev 01) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0, IRQ 20
        I/O ports at 6020 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
#2 (rev 01) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0, IRQ 21
        I/O ports at 6040 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
#3 (rev 01) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0, IRQ 17
        I/O ports at 6060 [size=32]

00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
#4 (rev 01) (prog-if 00 [UHCI])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0, IRQ 18
        I/O ports at 6080 [size=32]

00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI
Controller (rev 01) (prog-if 20 [EHCI])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0, IRQ 20
        Memory at e8584000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Debug port

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
(prog-if 01 [Subtractive decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=04, subordinate=08, sec-latency=32
        I/O behind bridge: 00007000-00007fff
        Memory behind bridge: e8100000-e83fffff
        Prefetchable memory behind bridge:
0000000040000000-0000000043f00000
        Capabilities: [50] #0d [0000]

00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface
Bridge (rev 01)
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0
        Capabilities: [e0] Vendor Specific Information

00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
Controller (rev 01) (prog-if 8a [Master SecP PriP])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 0, IRQ 16
        I/O ports at 01f0 [size=8]
        I/O ports at 03f4 [size=1]
        I/O ports at 0170 [size=8]
        I/O ports at 0374 [size=1]
        I/O ports at 60a0 [size=16]

00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family)
Serial ATA Storage Controller AHCI (rev 01) (prog-if 01 [AHCI 1.0])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
        I/O ports at 13f0 [size=8]
        I/O ports at 15f4 [size=4]
        I/O ports at 1370 [size=8]
        I/O ports at 1574 [size=4]
        I/O ports at 60d0 [size=16]
        Memory at e8585000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [80] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable-
        Capabilities: [70] Power Management version 2

01:00.0 Network controller: Broadcom Corporation Unknown device 4311
(rev 01)
        Subsystem: Hewlett-Packard Company Unknown device 1364
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e8000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] Message Signalled Interrupts: 64bit-
Queue=0/0 Enable-
        Capabilities: [d0] Express Legacy Endpoint IRQ 0

04:06.0 CardBus bridge: Texas Instruments Unknown device 8039
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 168, IRQ 17
        Memory at e8100000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=04, secondary=05, subordinate=08, sec-latency=176
        Memory window 0: 40000000-43fff000 (prefetchable)
        Memory window 1: 44000000-47fff000
        I/O window 0: 00007000-000070ff
        I/O window 1: 00007400-000074ff
        16-bit legacy interface ports at 0001

04:06.1 FireWire (IEEE 1394): Texas Instruments Unknown device 803a
(prog-if 10 [OHCI])
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 64, IRQ 18
        Memory at e8101000 (32-bit, non-prefetchable) [size=2K]
        Memory at e8104000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [44] Power Management version 2

04:06.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia
Card Reader (SD/MMC/MS/MS PRO/xD)
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 64, IRQ 10
        Memory at e8108000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [44] Power Management version 2

04:06.3 Class 0805: Texas Instruments Unknown device 803c
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, medium devsel, latency 64, IRQ 10
        Memory at e8109000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

04:06.4 Communication controller: Texas Instruments Unknown device 803d
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: medium devsel, IRQ 10
        Memory at e810a000 (32-bit, non-prefetchable) [size=4K]
        Memory at e810b000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [44] Power Management version 2

04:0e.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5788
Gigabit Ethernet (rev 03)
        Subsystem: Hewlett-Packard Company Unknown device 30aa
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
        Memory at e8110000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+
Queue=0/3 Enable-



------ 8< ------ 8< ------ 8< ------ 8< ------ 

Milan Avramovi?

System Engineer - Servers & OS


S&T Serbia d.o.o.
Narodnih heroja 43/XXIII
11070 Belgrade
Serbia

Tel.: +381-11-311 2908
Fax: +381-11-313 2052

mail: milan.avramovic at snt.co.yu
http://www.snt.co.yu




From dlclark at chtech.com  Mon Feb 26 16:08:39 2007
From: dlclark at chtech.com (David Clark)
Date: Mon, 26 Feb 2007 15:08:39 -0600
Subject: Yenta Socket work with 32-bit card but not 16-bit
In-Reply-To: <20070215182907.GA26928@isilmar.linta.de>
Message-ID: <007701c759ea$4b1d4fe0$0f01a8c0@longhorn>

We solved our issue; it ended up being a hardware problem.  A mistake
was made when designing the PCB.  Thank you for your assistance.

David Clark
Senior Software Engineer
C&H Technologies, Inc
Web: http:\\www.chtech.com
Phone: 512-733-2621
Fax: 512-733-2629
Email: dlclark at chtech.com
 

-----Original Message-----
From: linux-pcmcia-bounces at lists.infradead.org
[mailto:linux-pcmcia-bounces at lists.infradead.org] On Behalf Of Dominik
Brodowski
Sent: Thursday, February 15, 2007 12:29 PM
To: David Clark
Cc: linux-pcmcia at lists.infradead.org
Subject: Re: Yenta Socket work with 32-bit card but not 16-bit

Hi,

On Thu, Feb 15, 2007 at 12:18:20PM -0600, David Clark wrote:
> I may be way off track here and pleasae tell me if so.  From looking
at
> the source code in "rsrc_nonstatic.c" I gather that the first time the
> socket comes up, the kernel probes (do_mem_probe()) the PCI memory
space
> to find a suitable memory region which can be allocated to the PCMCIA
> cards.  

Right. Such mem resources are needed to access the card "CIS", too,
which in
turn is required to correctly determine which card this is.

> In my case 0x80000000-0xfcffffff is the entire memory range available
to
> the host PCI bridge.  Not all of this memory range is allocated to the
> various PCI devices, so why then does the memory probe not find any
> available resources?

Good question -- to which I don't really have an answer, unfortunately.
Could you try out what happens if you disable "CONFIG_ISA" in your
kernel
config (which in turn should switch of CONFIG_PCMCIA_PROBE)?

> Is this potentially related to my problem?  Again I'm trying my best
to
> understand how this all works.

Most likely this is the root of the problem.

	Dominik

_______________________________________________
Linux PCMCIA reimplementation list
http://lists.infradead.org/mailman/listinfo/linux-pcmcia



From brian_m600 at hotmail.com  Wed Feb 28 00:01:10 2007
From: brian_m600 at hotmail.com (Sir Brian Moffat)
Date: Wed, 28 Feb 2007 06:01:10 +0100 (CET)
Subject: CONTACT ME
Message-ID: <20070228050110.81D32702423@3468.mega-host.de>


Sir Brian Moffat 
Head Investigation Dept, 
HSBC Bank plc 
8 Canada Square 
London E14 5HQ 
England. 

SUBJECT: BENEFICIARY SUM OF 30 MILLION POUNDS STERLING GB. 

I am seeking for your co-operation to present you to my bank as the next of kin/will beneficiary to Mrs. Sigrid Fassnacht, a foreign contractor from Cologne, Germany who died on a plane crash on July 25th 2000 with her husband Rudi Fassnacht. Her husband and their two children also perished in the air FranceConcorde New York bound flight,pleaseclickhereforverification

http://news.bbc.co.uk/1/hi/world/europe/859479stm

Before her death, she was a contractor to British National Petroleum Co-operation (BNPC) and has a bank balance with my bank to the tune of (30 million poundssterling GBP) which will be paid to you as her next of kin/will beneficiary. For your information, I am the Head of Investigation Department with HSBC Bank Plc London. 

The board of directors of HSBC Bank Plc which I am also a member, mandated me to look for any known relation of Mrs.Sigrid Fassnacht, since after her death. However, all my efforts traces abortive, that is the main reason I am writing you this to askforyour co-operation for us to claim this money because it will amount to injustice if I do not take this decisive step to secure this deposit and invest it, because if nobody comes forward to claim the fund it will be forfeited to the government, based on that I have contacted you to assist me in making this transaction a reality. 

I only have to approve you as the next of kin/will beneficiary and the fund will be paid to you as the beneficiary. We are to share this money between ourselves and also donate 10% to charity and the tsunami victims if you are really interested in this offer you should contact me through this email address:moffat2007 at katamail.com

For detail of this transaction and procedures, please do forward me your full address, phone number/mobile number,your company name or occupation these info will enable me commence immediately to secure all legal documents in your favor on your acceptance to fully cooperate with me.I await your urgent response at my private email moffat2007 at katamail.com to enable us jumpstart this project and nurture 
it to reality. 

Yours faithfully, 

Sir Brian Moffat, 
Head Investigation Dept, 
HSBC Bank plc 
8 Canada Square 
London E14 5HQ 
England. 















From ma.alvarez at ziv.es  Wed Feb 28 05:03:49 2007
From: ma.alvarez at ziv.es (Miguel Angel Alvarez)
Date: Wed, 28 Feb 2007 11:03:49 +0100
Subject: Conflict in the second port of Novatel Wireless?
Message-ID: <45E55385.6060606@ziv.es>

Hi

I have upgraded my system based in a MFC5200 (power pc) from linux 
2.6.15 and pcmcia-cs to 2.6.20 and pcmciautils.

I work with different pcmcia cards, and have not encountered problems 
but in one (Novatel U630).

In the past, just one serial port is found, and everything worked. Now, 
two serial ports are found; one is asigned to ttyS0 and the second to 
ttyS1. However, when I try to send AT commands to one of them, they fail.

I have been digging into the code, and see nothing strange, so finally 
yesterday I decided to hack ds.c and its bus_match function to skip the 
matching of the second port.

Now the first port works... Any clues?

Thanks

Miguel ?ngel ?lvarez 
 
----------------------------------------- PLEASE NOTE -------------------------------------------
This message, along with any attachments, may be confidential or legally privileged. 
It is intended only for the named person(s), who is/are the only authorized recipients.
If this message has reached you in error, kindly destroy it without review and notify the sender immediately.
Thank you for your help.
ZIV uses virus scanning software but excludes any liability for viruses contained in any attachment.
 
------------------------------------ ROGAMOS LEA ESTE TEXTO -------------------------------
Este mensaje y sus anexos pueden contener informaci?n confidencial y/o con derecho legal. 
Est? dirigido ?nicamente a la/s persona/s o entidad/es rese?adas como ?nico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim?nelo sin revisarlo ni reenviarlo y notif?quelo inmediatamente al remitente. Gracias por su colaboraci?n.  
ZIV utiliza software antivirus, pero no se hace responsable de los virus contenidos en los ficheros anexos.


From invest_loanoffer13 at yahoo.co.uk  Wed Feb 28 23:39:00 2007
From: invest_loanoffer13 at yahoo.co.uk (INTEREST)
Date: Thu,  1 Mar 2007 05:39:00 +0100 (CET)
Subject: LOAN OFFER................LOW  INTEREST
Message-ID: <20070301043900.6EBB64A52C6@ema-hosting.de>



 

    I give out loan to Business Men and Women who are into Business transaction, I give out long term loan for three to five years maximum with your interest in this you can as well tell me the amount you need so that I send to you the terms and condition that is if you are really interested in getting a loan from me, Loan is given out in Pounds Sterling ( ? ) and $US Dollars the maximum I give is 5,000,000 both in Pounds Sterling ( ? ) and $US and the minimum 5,000 Pounds Sterling ( ? ) and US$ so if really you are interested mail for more info on how the loan can be transferred to you. 

 

There is one Question I have to ask are you a serious individual that we take a loan and pay back after duration with the interest, if you are honest I will trust you because I like to do business with Honest people if you are one you will get the loan with out problem and for your information if you should want more loan like $50,000,000m I can give only if you are one of these categories: Manager of a company A private Holder A broker in banks A director in any office or company A high investor of a company If you are one of the following you can get $50,000,000US as loan or if personal loan you can request for 5,000-5,000,000 as loan. Hope to hear from you soon. Name In 

 

Full: ___________________________________

Occupation: ____________________________

Country: _______________________________

State: _________________________________

City: __________________________________

Zip code: _____________________________

Phone Number: ________________________

Sex: __________________________________

 

Send these info it is important. Mind you loans are given to every part of the world only if I see you to be honest and will pay back after duration. If you are interested you have to send the amount you need as loan so that I can give you the terms and condition on the loan for your information loan are given to every part of the world to honest people so if you are honest apply for the loan now. Email. invest_loanoffer13 at yahoo.co.uk.

 Thanks and Have a nice day






