Re: pcmciautils.git

2012-03-16 Thread Komuro
Hi, I stil can't find the http://kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

pcmciautils.git

2012-02-10 Thread Komuro
Hi, Currently, I can't find git://git.kernel.org/pub/scm/linux/pcmcia/pcmciautils.git/ and "Linux Kernel 2.6 PCMCIA" site. ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

[pcmciautils] hotplug is obsolete?

2011-08-06 Thread Komuro
Hi, It seems hotplug is obsolete. If yes, hotplug-script should be removed from pcmciautils? Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

ide-cs driver

2011-08-01 Thread Komuro
Hi, ide-cs driver is old and un-maintained. so I think ide-cs should have been removed when Linux becomes ver 3.0. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: Re: Lecture of German

2011-08-01 Thread Komuro
>> In a letter to Max Born, Einstein wrote: >> "Der Alte nicht würfelt." >> >> In English, "He [God] does not throw dice." >> >> Does "der Alte" mean God in German? >> >> According to the dictionary, Alte means old. > >I'm not an expert in German, but I'll try here. The word "alte" is an adjecti ve

Lecture of German

2011-07-31 Thread Komuro
Dear expert of German. In a letter to Max Born, Einstein wrote: "Der Alte nicht wurfelt." In English, "He [God] does not throw dice." Does "der Alte" mean God in German? According to the dictionary, Alte means old. Best Regards Komuro ___

Lecture of German

2011-07-31 Thread Komuro
Dear expert of German. In a letter to Max Born, Einstein wrote: "Der Alte nicht würfelt." In English, "He [God] does not throw dice." Does "der Alte" mean God in German? According to the dictionary, Alte means old. Best Regards Komuro ___

Re: Re: Re: [ds.h] need WIN_FLAGS_WIN_0, 1, 2, 3 definition

2011-07-24 Thread Komuro
Hi, >Is there a problem with that? currently, there is no problem. >Hey, > >On Sun, Jul 24, 2011 at 08:08:11PM +0900, Komuro wrote: >> For example, >> when we use the resource[2], we should set WIN_FLAGS_WIN_2 >> to link->resource[2]->flags ? > >N

Re: Re: [ds.h] need WIN_FLAGS_WIN_0, 1, 2, 3 definition

2011-07-24 Thread Komuro
;resource[2]->end = 0; i = pcmcia_request_window(link, link->resource[2], 0); > >Hey Komuro, > >On Sun, Jul 24, 2011 at 12:28:10PM +0900, Komuro wrote: >> Hi, >> >> I think we need WIN_FLAGS_WIN_0, 1, 2, 3 definition below >> >> any comment?

[ds.h] need WIN_FLAGS_WIN_0, 1, 2, 3 definition

2011-07-23 Thread Komuro
ne WIN_FLAGS_WIN_20x0c +#define WIN_FLAGS_WIN_30x10 /* config_reg{ister}s present for this PCMCIA device */ #define PRESENT_OPTION 0x001 Best Regards Komuro [I changed my e-mail address.] ___ Linux PCMCIA rei

Re: Re: [ANNOUNCE] pcmciautils-018 released

2011-04-24 Thread Komuro
Hi, It seems recent modprobe does not have -b option. but older version of modprobe seems to have it. >> [rules-base] >> >> ># PCMCIA sockets: >> ># >> ># modprobe the pcmcia bus module so that 16-bit PCMCIA devices work >> >SUBSYSTEM=="pcmcia_socket", \ >> >RUN+="/sbin/modprobe

pccardctl config

2011-04-24 Thread Komuro
Hi, ># pccardctl config >Socket 0: >command 'config' not yet handled by pccardctl If no one will add 'config' option, it should be removed from pccardctl source code. Best Regards Komuro ___ Linux PCMC

Re: [ANNOUNCE] pcmciautils-018 released

2011-04-24 Thread Komuro
Hi, [rules-base] ># PCMCIA sockets: ># ># modprobe the pcmcia bus module so that 16-bit PCMCIA devices work >SUBSYSTEM=="pcmcia_socket", \ >RUN+="/sbin/modprobe -b pcmcia" The modprobe does not have -b option. ___ Linux PCMCIA reimpl

[PATCH 2.6.36-git1]pd6729:Coding Style fixes

2010-10-22 Thread Komuro
pd6729: remove unnecessary space. Signed-off-by: Komuro --- --- linux-2.6.36-git1/drivers/pcmcia/pd6729.c.orig 2010-10-22 21:38:04.0 +0900 +++ linux-2.6.36-git1/drivers/pcmcia/pd6729.c 2010-10-22 21:38:38.0 +0900 @@ -725,17 +725,17 @@ static int __devinit

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-19 Thread Komuro
Hi, > http://userweb.kernel.org/~brodo/pcmcia-2.6.35.diff Serial part of Xircom card works with pcmcia-2.6.35.diff. - Original Message - >Date: Sat, 18 Sep 2010 15:32:12 +0200 >From: Dominik Brodowski >To: Komuro , pa...@ucw.cz >Cc: linux-pcmcia@lists.infradead.o

Re: Re: Re: Re: Re: Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-18 Thread Komuro
gister) of irq is not properly setup, we can see the above message... >Hey, > >On Sat, Sep 18, 2010 at 07:20:31PM +0900, Komuro wrote: >> With this patch, fmvj18x_cs based card works (both network and serial). > >good. Will push the patch upstream, then. > >> but Seri

Re: Re: Re: Re: Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-18 Thread Komuro
1:48:32AM +0900, Komuro wrote: >> Attached file is dmesg of another multi-function card(fmvj18x_cs) > >Thanks for the debug output -- this helps a lot! > >> This card works with 2.6.35 >> but does not work with 2.6.36rc3(+patch). > >does this patch help (at least with

Re: Re: Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-17 Thread Komuro
Hi, >Are these lines different from what you see on a working kernel? dmesg is same between working kernel and 2.6.36-rc3. but 2.6.36-rc3(+patch) , the serial part still does not work. - Original Message - >Date: Fri, 17 Sep 2010 20:52:12 +0200 >From: Dominik Brodowski &g

Re: Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-17 Thread Komuro
Hi, Xircom multi-function card still does not work. Please see the attached dmesg log. Best Regards Komuro - Original Message - >Date: Mon, 13 Sep 2010 21:53:53 +0200 >From: Dominik Brodowski >To: Komuro >Cc: linux-pcmcia@lists.infradead.org, linux-ser...@vger.kernel.

Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-07 Thread Komuro
Hi, Attached file is the output of /sys/kernel/debug/dynamic_debug/control. kernel 2.6..36-rc3. xirc2pcs_cs multi-function card. # filename:lineno [module]function flags format arch/x86/kernel/cpu/perfctr-watchdog.c:244 [perfctr_watchdog]write_watchdog_counter - "setting %s to -0x%08Lx\012" a

Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-09-04 Thread Komuro
Hi, > >$ echo "module pcmcia +p" > /sys/kernel/debug/dynamic_debug/control > Which kernel .config option do I need to enable dynamic_debug? My kernel does not have /sys/kernel/debug/dynamic_debug/control. ___ Linux PCMCIA reimplementation list http:

Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-08-31 Thread Komuro
and we should also >set the port address to the beginning, and not the end of >the 8-port range. > >Reported-by: Komuro >Signed-off-by: Dominik Brodowski > >diff --git a/drivers/serial/serial_cs.c b/drivers/serial/serial_cs.c >index 141c695..dd0fa12 100644 >--- a/dri

[BUG] [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-08-27 Thread Komuro
Hi, Something is strange in pcmcia_request_configuration? at kernel 2.6.36-rc1? serial part of multi-function card does not work at 2.6.36-rc1. output of /proc/ioports [2.6.36-rc1] 02e8-02ef : pcmcia_socket0 02e8-02ef : pcmcia0.0 02e8-02ef : serial 0300-030f : pcmcia_socket0 0300-0

Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-08-20 Thread Komuro
Hi >@@ -463,13 +463,13 @@ static int simple_config(struct pcmcia_device *link) > /* If the card is already configured, look up the port and irq */ > if (link->function_config) { > unsigned int port = 0; >- if ((link->io.BasePort2 != 0) && >-

Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-08-20 Thread Komuro
Hi >--- a/drivers/serial/serial_cs.c >+++ b/drivers/serial/serial_cs.c >@@static int serial_probe(struct pcmcia_device *link) > info->p_dev = link; > link->priv = info; > >- link->io.Attributes1 = IO_DATA_PATH_WIDTH_8; >- link->io.NumPorts1 = 8; >+ link->resource[0]->fl

Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-08-13 Thread Komuro
Hi, >@@ -248,9 +248,8 @@ static int fmvj18x_probe(struct pcmcia_device *link) > lp->base = NULL; > > /* The io structure describes IO port mapping */ >-link->io.NumPorts1 = 32; >-link->io.Attributes1 = IO_DATA_PATH_WIDTH_AUTO; >-link->io.IOAddrLines = 5; >+link->resource[

Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()

2010-08-08 Thread Komuro
} > printk(KNOT_XIRC "no ports available\n"); > } else { >- link->io.NumPorts1 = 16; >+ link->io_lines = 10; >+ link->resource[0]->end = 16; Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [PATCH 01/11] pcmcia: use pcmica_{read,write}_config_byte

2010-08-02 Thread Komuro
Hi, >--- a/drivers/net/pcmcia/xirc2ps_cs.c >+++ b/drivers/net/pcmcia/xirc2ps_cs.c >+ if (err) > goto config_error; >- reg.Action = CS_WRITE; >- reg.Offset = CISREG_IOBASE_1; >- reg.Value = (link->io.BasePort2 >> 8) & 0xff; >- if ((err = pcmcia_access_configurat

ds.h: unnecessary bit-field

2010-07-24 Thread Komuro
Hi, bit-field sometimes introduces locking problem. for example, if one cpu loads the value "suspended", it also loads other value ("_irq", "_io" ..) at the same time. so it should not be used? [include/pcmcia/ds.h] u16 suspended:1; /* Flags whether io, irq

Re: Re: ss.h: unnecessary bit-field

2010-07-22 Thread Komuro
Hi, >> include/pcmcia/ss.h >> >> >/* socket setup is done so resources should be able to be allocated. >> > * Only if set to 1, calls to find_{io,mem}_region are handled, and >> > * insertio events are actually managed by the PCMCIA layer.*/ >> >u8 res

ss.h: unnecessary bit-field

2010-07-17 Thread Komuro
Hi, include/pcmcia/ss.h > /* socket setup is done so resources should be able to be allocated. >* Only if set to 1, calls to find_{io,mem}_region are handled, and >* insertio events are actually managed by the PCMCIA layer.*/ > u8 resource_

Re: Re: [BUG?] pcmcia: IO port probe is broken on 2.6.35-rc2?

2010-06-12 Thread Komuro
Hi, /proc/ioports between 2.6.34. and 2.6.35-rc2 is same. Currently I can't reproduce this problem. - : PCI Bus #00 -001f : dma1 0020-0021 : pic1 0040-0043 : timer0 0050-0053 : timer1 0060-0060 : keyboard 0064-0064 : keyboard 0080-008f : dma page reg 00a0-00a1 : pic2

[BUG?] pcmcia: IO port probe is broken on 2.6.35-rc2?

2010-06-11 Thread Komuro
t1: cs: IO port probe 0x820-0x8ff: excluding 0x820-0 x87f pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean. Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

[BUG] pcmcia: dev_node removal (drivers with unregister_netdev check)

2010-06-06 Thread Komuro
Dear Dominik You introduced a bug to smc91c92_cs.c link->priv = dev; is necessary at smc91c92_probe. --- a/drivers/net/pcmcia/smc91c92_cs.c +++ b/drivers/net/pcmcia/smc91c92_cs.c @@ -103,7 +103,6 @@ struct smc_private { u_shortmanfid; u_short

Re: Questions about ioport-assignments

2010-05-09 Thread Komuro
e_resource(base, size, type | IORESOURCE_BUSY, name); if (res) { #ifdef CONFIG_PCI if (s && s->cb_dev) parent = pci_find_parent_resource(s->cb_dev, res); #endif Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: Re: Re: Re: Re: [BUG? KERNEL 2.6.34-rc5-git5] pccard_validate_cis WARN_ON error

2010-05-04 Thread Komuro
socket_suspend(skt); >+ msleep(100); >+ } >+ } >+ if ((sysfs_events & PCMCIA_UEVENT_RESUME) && >+

[BUG: invalid hash] - update pata_pcmcia/ide-cs with transcend and kingston cards

2010-05-02 Thread Komuro
0x2e6d1829, 0xacbe682e), >> PCMCIA_DEVICE_PROD_ID12("IO DATA", "CBIDE2 ", 0x547e66dc, 0x8671043 b), >> PCMCIA_DEVICE_PROD_ID12("IO DATA", "PCIDE", 0x547e66dc, 0x5c5ab149), >> @@ -444,6 +446,8 @@ static struct pcmcia_device_id pcmc

Re: Re: Re: Re: [BUG? KERNEL 2.6.34-rc5-git5] pccard_validate_cis WARN_ON error

2010-04-30 Thread Komuro
Hi, >> But, after "pccardctl reset", the card still does not work. > >Why is "pccardctl reset" needed in any case? When the device becomes unstable, "pccardctl reset" reset the driver. >It seems that the CIS is >different when you call "pccardctl reset" compared to what it used to be. The CIS

Re: Re: Re: [BUG? KERNEL 2.6.34-rc5-git5] pccard_validate_cis WARN_ON error

2010-04-29 Thread Komuro
Hi, >> >> WARNING: at drivers/pcmcia/cistpl.c:1488 pccard_validate_cis+0x32/0x2c6( ) >> > >> >is a call trace printed? If so, what is it? >> >> Here is the call trace. > >Thanks! Does this patch help? > The WARN_ON error is fixed. But, after "pccardctl reset", the card still does not work. cas

Re: Re: [BUG? KERNEL 2.6.34-rc5-git5] pccard_validate_cis WARN_ON error

2010-04-29 Thread Komuro
Hi, >> >> WARNING: at drivers/pcmcia/cistpl.c:1488 pccard_validate_cis+0x32/0x2c6() > >is a call trace printed? If so, what is it? > Here is the call trace. [ cut here ] WARNING: at drivers/pcmcia/cistpl.c:1488 pccard_validate_cis+0x32/0x2c6() Hardware name: System Produ

[BUG? KERNEL 2.6.34-rc5-git5] pccard_validate_cis WARN_ON error

2010-04-28 Thread Komuro
return -EINVAL; } Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [PATCH] pcmcia: fix matching rules for pseudo-multi-function cards

2010-04-28 Thread Komuro
>here is a fix for the rule to prevent PCMCIA_DEV_ID_MATCH_FUNC_ID entries >to match on PFC-cards. e.g. serial_cs PCMCIA_DEVICE_FUNC_ID(2) >will match on device 0 of a xircom CEM33 card resulting in a >failure in xirc2ps_cs. >I changed the code, so that the first matching struct pcmcia_device_id

Re: Questions about ioport-assignments

2010-04-17 Thread Komuro
Hi, >Hm, I don't get (yet) where you're heading to -- could you provide me with a >patch and/or more extensive explanation? OK. Here is the patch. pci_bus_alloc_resource calls pcmcia_align with res->start=0xc000. To avoid this , we need to call pcmcia_align manually. --- linux-2.6.34-rc4-git

Re: Questions about ioport-assignments

2010-04-17 Thread Komuro
Hi, [solution] If we have two io-resource io-res1, io-res2 (for example) we try to allocate io-resource from io-res2(lower ioport). if it fails , try to allocate io-resource from io-res1. io-res1 0xc000-0xcfff io-res2 0x0100-0x03ff ___ Linux PCM

Re: Questions about ioport-assignments

2010-04-16 Thread Komuro
Hi, sorry, "lines" seems to be align. but some devices with lines=10, it means max io-port = 0x3ff. ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: Questions about ioport-assignments

2010-04-16 Thread Komuro
Hi, >That's not pcmcia_common_align()s fault -- but this line in alloc_io_space: > > align = (*base) ? (lines ? 1< >Should we try replacing it with > > align = lines ? 1 << lines : 0; > >unconditionally? In this case, *base = 0x300 So align = (*base) ? (lines ? 1

Re: Questions about ioport-assignments

2010-04-16 Thread Komuro
esource_size_t start) { resource_size_t ret; /* * Ensure that we have the correct start address */ ret = (start & ~align_data->mask) + align_data->offset; if (ret < start) ret += align_data->mask + 1; return ret; } Best Re

Re: pci_bus_for_each_resource, transparent bridges and rsrc_nonstatic.c

2010-04-15 Thread Komuro
Hi, After setting start = 0x100, size becomes wrong value... unsigned long size = end - start + 1; <=== HERE int ret = 0; +#if defined(CONFIG_X86) + /* on x86, avoid anything < 0x100 for it is often used for +* legacy platform devices */ + if (sta

Re: [kernel 2.6.34-rc2] cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f

2010-04-10 Thread Komuro
Hi, >> So I think this is a pcmcia_core problem not _CRS / ACPI. >> >> It was reliably detected by io_probe before. > >I think we got hit by the same issue as at commit >7a96e87d6e58a07235a2bc3eff9b093af4937a72 . Could you test this patch, >please? OK. works. pcmcia_socket pcmcia_socket1: cs:

Re: [kernel 2.6.34-rc2] cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f

2010-04-08 Thread Komuro
37a => c4 0x37b => ff 0x37c => ff 0x37e => ff 0x37f => ff It means this area is _not_ clean. So I think this is a pcmcia_core problem not _CRS / ACPI. It was reliably detected by io_probe before. Best Regards Komuro _

Re: [PATCH] pcmcia: fix up alignf issues

2010-04-05 Thread Komuro
Hi, >> cf->io.win[0].base returns 0 at smc_configcheck(); >> So I think this is a pcmcia_request_io problem. > >Actually, it seems to be an issue with rsrc_nonstatic. Attached is a patch >for 2.6.34-rc; OK. works. ___ Linux PCMCIA reimplementation lis

Re: [BUG? kernel 2.6.33] Bogus ioport is allocated for pcmcia device

2010-04-04 Thread Komuro
8, 0x0103 offset 0x76, tuple 0x14, link 0x00 no_long_link Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [BUG] [RFC PATCH 07/19] pcmcia: re-work pcmcia_request_irq()

2010-04-03 Thread Komuro
Hi, >do you mean this? > > >diff --git a/drivers/pcmcia/pcmcia_resource.c >b/drivers/pcmcia/pcmcia_resource.c >index bb927ed..63d09df 100644 >--- a/drivers/pcmcia/pcmcia_resource.c >+++ b/drivers/pcmcia/pcmcia_resource.c >@@ -452,7 +452,8 @@ int pcmcia_request_configuration(struct pcmcia_device

[BUG] [RFC PATCH 07/19] pcmcia: re-work pcmcia_request_irq()

2010-04-02 Thread Komuro
Hi, no interrupt is delivered to the pcmcia card. I think pcmcia_request_configuration does not setup irq properly. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [kernel 2.6.34-rc2] cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f

2010-03-27 Thread Komuro
Hi, >Can't see how this is a real PCMCIA issue here... You are right. do_io_probe (in rsrc_nonstatic.c) is not changed between 2.6.33 and 2.6.34-rc2... ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [kernel 2.6.34-rc2] cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f

2010-03-27 Thread Komuro
Hi, >What kind of device is at 0x378? Was it reliably detected by io_probe >before? Why is this device not reported by _CRS / ACPI / whatever? 0x378 is printer-port. Here is the dmesg of 2.6.34-rc2. Linux version 2.6.34-rc2 (r...@localhost.localdomain) (gcc version 4.1.2 20070502 (Red Hat 4.1

[kernel 2.6.34-rc2] cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f

2010-03-26 Thread Komuro
pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean. pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. Best Regards Komuro

Re: [BUG? kernel 2.6.34-rc1-git8] cs: IO port probe 0x0-0xcf7: clean.

2010-03-23 Thread Komuro
S. I'm not sure the recent system have PNP BIOS. Another solution is to use ACPI BIOS. but pre-1998 system does not have ACPI BIOS. ISA slot card is no longer sold in the PC store, but on-board legacy devices still use this lower ioport. Best Reg

Re: [BUG? kernel 2.6.34-rc1-git8] cs: IO port probe 0x0-0xcf7: clean.

2010-03-22 Thread Komuro
Hi, >> Actually, ioport 0x0-0xff is used for onboard legacy devices. >> So it should be excluded? > >Probably -- and none of the devices listed below seem to actually be PCI >devcices... However, I have no idea why there is a "PCI Bus :00" here. >Oh wait. Is this the PC in which both pd6729 an

Re: [BUG? kernel 2.6.34-rc1-git8] cs: IO port probe 0x0-0xcf7: clean.

2010-03-21 Thread Komuro
Hi, >> I don't add "include port 0x0-0xcf7" in /etc/pcmcia/config.opts. >> but recent kernel probes this ioport range ... > >That's because the parent PCI bridge offers these resources for downstream >users, such as yenta_cardbus. So that's not a bug. Actually, ioport 0x0-0xff is used for onboar

[BUG? kernel 2.6.34-rc1-git8] cs: IO port probe 0x0-0xcf7: clean.

2010-03-20 Thread Komuro
Hi, I don't add "include port 0x0-0xcf7" in /etc/pcmcia/config.opts. but recent kernel probes this ioport range ... yenta_cardbus :04:06.0: CardBus bridge found [1179:ff66] yenta_cardbus :04:06.0: ISA IRQ mask 0x0ca8, PCI irq 18 yenta_cardbus :04:06.0: Socket status: 3410 yenta_

[PATCH kernel 2.6.34-rc1-git7] pd6729: Coding Style fixes

2010-03-19 Thread Komuro
Signed-off-by: Komuro --- --- linux-2.6.34-rc1/drivers/pcmcia/pd6729.c.orig2 2010-03-14 05:45:04.0 +0900 +++ linux-2.6.34-rc1/drivers/pcmcia/pd6729.c2010-03-19 06:24:16.0 +0900 @@ -14,13 +14,13 @@ #include #include #include +#include #include #include

Re: [BUG? kernel 2.6.33] Bogus ioport is allocated for pcmcia device

2010-03-14 Thread Komuro
rd. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

[BUG? kernel 2.6.33] Bogus ioport is allocated for pcmcia device

2010-03-13 Thread Komuro
Hi, Bogus ioport is allocated for pcmcia device at kernel 2.6.33. ioport is 0x30 but it should be 0x100. [2.6.33] ata5: PATA max PIO0 cmd 0x30 ctl 0x3e irq 17 ata5.00: CFA: , Ver.1.0, max PIO2 ata5.00: 32000 sectors, multi 0: LBA ata5.00: configured for PIO0 ata5.00: configured for PIO0 ata5: E

Re: [Another BUG? kernel 2.6.34-rc1] cs: warning: no high memory space available!

2010-03-13 Thread Komuro
socket[i].socket.pci_irq = dev->irq; >+ socket[i].socket.cb_dev = dev; Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [Another BUG? kernel 2.6.34-rc1] cs: warning: no high memory space available!

2010-03-13 Thread Komuro
Hi, >... and a full dmesg output, if possible. Note: In my PC, pd6729 and yenta_socket are installed. [2.6.34-rc1] Linux version 2.6.34-rc1 (r...@localhost.localdomain) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Sat Mar 13 09:59:12 JST 2010 BIOS-provided physical RAM map: BIOS-e820

Re: [Another BUG? kernel 2.6.34-rc1] cs: warning: no high memory space available!

2010-03-13 Thread Komuro
Hi, >a) do the cards still work? They do _not_ work on pd6729. >b) what's the output of cat /proc/iomem (2.6.34-rc1)? The difference is "4000- : PCI Bus #00" [2.6.34-rc1] - : reserved 0001-0009fbff : System RAM 0009fc00-0009 : reserved 000a-000b : PC

[Another BUG? kernel 2.6.34-rc1] cs: warning: no high memory space available!

2010-03-13 Thread Komuro
Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

[PATCH kernel 2.6.33] pd6729: remove irq_list parameter

2010-02-27 Thread Komuro
pd6729: remove irq_list parameter. it should be set by /etc/pcmcia/config.opts. Signed-off-by: Komuro --- --- linux-2.6.33/drivers/pcmcia/pd6729.c.orig 2010-02-28 08:36:55.0 +0900 +++ linux-2.6.33/drivers/pcmcia/pd6729.c2010-02-28 08:41:55.0 +0900 @@ -48,23

Re: Questions about ioport-assignments

2010-02-21 Thread Komuro
s (after applying the patch to make my D-Link DMF560TX >work): Could you post the patch you made for D-Link DMF560TX? This problem is not fixed yet. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

[Error] cs: warning: no high memory space available!

2010-02-20 Thread Komuro
Hi, After "pccardctl" eject and "pccardctl insert", I get the message "cs: warning: no high memory space available!" in the PCMCIA patches(brodo/pcmcia-2.6.git). >pcmcia_socket pcmcia_socket0: parse_uevents: events 0002 >pcmcia_socket pcmcia_socket0: insert >pcmcia_socket pcmcia_socket0: set

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-02-20 Thread Komuro
e conf->ConfigIndex of the 3com card > is not set up properly... >but that is statically set to "1" in 3c589_cs.c? I'm a bit confused... I set the ConfigIndex = 7 in 3c589_cs.c. 3CXEM556 works now. -link->conf.ConfigInd

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-02-20 Thread Komuro
3com card is not set up properly... Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-02-19 Thread Komuro
Hi, > >these were, again, very valuable debug hints. Based on those I've upgraded > >my patches in the git repository. It'd be great if yo could re-run the test > >once again, ad still with the debug patch applied. (1) it seems the 3c562 multi_function card works now. (2) but another 3com car

Fw: Re: [patch 1/1] drivers/pcmcia/yenta_socket.c: ENE CB712 CardBus bridge needs special treatment with Echo Audio Indigo soundcards

2010-02-19 Thread Komuro
E, PCI_DEVICE_ID_ENE_1211, ENE), > > not removed. It is replaced by next line. Best Regards Komuro -- Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-02-17 Thread Komuro
Hi, >these were, again, very valuable debug hints. Based on those I've upgraded >my patches in the git repository. It'd be great if yo could re-run the test >once again, ad still with the debug patch applied. There is no updated patch in brodo/pcmcia-2.6.git?

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-02-02 Thread Komuro
Hi, When the 3com card does not work, the card_id and prod_id becomes the bogus value. The card_id should be 0x0562. the prod_id(2) should be "3C562D/3C563D" [Socket 0 Bridge: [yenta_cardbus] (bus ID: :04:06.0) Configuration: state: on ready: yes

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-01-29 Thread Komuro
Hi, I tried the current(2010/02/29) brodo/pcmcia-2.6.git#master. The problem still happens. >> lspcmcia -vvv is same between before and after re-plug. > >Are the drivers bound before the re-plug? Now, with v4, does it work >out-of-the-box or does it work if you issue a > > echo 1 > > /s

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-01-20 Thread Komuro
Hi, The exported function should be locked like below? size_t pcmcia_get_tuple(struct pcmcia_device *p_dev, cisdata_t code, unsigned char **buf) { struct pcmcia_loop_get get = { .len = 0, .buf = buf, }; + mutex_l

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-01-19 Thread Komuro
Hi, > > The 3c589_cs and serial_cs is not loaded at dmesg below. > > After re-plug, it works. > > Strange -- what does "lspcmcia -vvv" look like before and after re-plug? lspcmcia -vvv is same between before and after re-plug. By the way, the pcmcia-socket-startup is loaded after registering n

Re: [RFC v3] PCMCIA locking updates for 2.6.34

2010-01-19 Thread Komuro
pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [RFC] PCMCIA locking updates for 2.6.34

2010-01-16 Thread Komuro
Hi, Same result as Wolfram. > "echo d > /proc/sysrq-trigger" No output from sysrq-trigger. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 pcmcia 0.1: pcmcia: registering new device pcmcia0.1 INFO: task modprobe:2191 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_ta

Re: Questions about ioport-assignments

2010-01-15 Thread Komuro
;> Some pcmcia-card decodes only lower 10bits (0x-0x03FF). >> Such card does not work on higher ports (0x0400-0x) >> > >Quick'n'Dirty patch -- or should we handle this generically, Komuro? Any way >to reliably detect these cards? I think your patch is not c

RE: Questions about ioport-assignments

2010-01-14 Thread Komuro
x03FF). Such card does not work on higher ports (0x0400-0x) So your card is not a buggy card. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia

Re: [PATCH V2] pcmcia/yenta: add module parameter for O2 speedups

2010-01-10 Thread Komuro
and decide accordingly. Fixes Bugzilla entry 15014. > >Simplify and unify the printouts, fix a whitespace issue while we are here. > >Signed-off-by: Wolfram Sang >Tested-by: frod...@gmail.com >Cc: Dominik Brodowski >--- Best Regards Komuro _

Re: Re: Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2010-01-09 Thread Komuro
Hi, >> >I have a bad feeling about this... might it be that cistpl.c isn't thread >> >safe at all? >> > >> >Could you test out this patch, please? >> With this patch, the 3c589_cs driver is not loaded at all. So I think this patch is not correct. >pcmcia_socket pcmcia_socket0: pccard: PCMCIA ca

Re: Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2010-01-09 Thread Komuro
Hi, >I have a bad feeling about this... might it be that cistpl.c isn't thread >safe at all? > >Could you test out this patch, please? OK. I will test it. By the way , do you think the pcmcia_core API is MP safe ? I need to learn the difference between spin_lock and mutex_lock.

Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2010-01-07 Thread Komuro
Hi, I got the kernel-oops by pcmcia-check-broken-cis at kernel 2.6.33-rc3. Do you think this is the same as CIS problem? pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 pcmcia_socket pcmcia_s

Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS

2010-01-03 Thread Komuro
Hi, I can't reproduce the CIS problem now. Below is the dmesg I got before. I think 3c589_cs is loaded before memory resource is ready. pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pcmcia_socket pcmcia_socket0: cs: memory probe 0xd200-0xd40f: excludin g 0x

Re: Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS

2010-01-01 Thread Komuro
>>This can be (and probably is) totally unrelated, but e.g. in Fedora 10 >>somewhere in their 2.6.27.xx kernel series updates, my USB 3G modem >>stopped to work if it was plugged to USB port at the boot time. After >>booting, doing unplug->replug it started to work normally. >> >>I just wonder i

Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS

2010-01-01 Thread Komuro
gt; >I just wonder if there is something wrong in the kernel hotplug system >or something. > Yes. Actually, if I connect the USB CDROM and boot linux, the USB CDROM is not detected and I need to replug it. So I think at least USB device support of udev has th

Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS

2010-01-01 Thread Komuro
Hi, >Good to know it's reproducible... Does issuing > ># pccardctl eject ># pccardctl insert > >without actually ejecting and inserting the card fix the issue you're >seeing? > afer pccardctl eject, pccardctl insert, the card works. ___ Linux PCMCIA

Re: [PATCH 1/2] pcmcia: remove unused IRQ_FIRST_SHARED

2009-12-30 Thread Komuro
Hi, In drivers/net/pcmcia/smc91c92_cs.c, one IRQ_FIRST_SHARED is not removed yet. (1) static int osi_config(struct pcmcia_device *link) { struct net_device *dev = link->priv; static const unsigned int com[4] = { 0x3f8, 0x2f8, 0x3e8, 0x2e8 }; int i, j; link->conf.Att

Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS

2009-12-30 Thread Komuro
Hi, > >what's the difference between "lspcmcia -vvv" when the problem exists, and >when the problem does not appear? Can you read out the CIS via sysfs even >when the problem exists, and is it the same as when the problem does not >appear? The "lspcmcia -vvv" is same between the problem appear a

[ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS

2009-12-23 Thread Komuro
Hi, The problem below is CIS problem and no relation with kernel/resource.c. This problem is introduced at kernel 2.6.32 or earlier. >but if I connect the 3Com 3c562 and boot the linux, >the mac address of 3c562 sometimes becomes ff:ff:ff:ff:ff:ff. >the mac address becomes normal after replug

Re: Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2009-12-20 Thread Komuro
pcmcia: registering new device pcmcia0.1 >0.1: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A >3c589_cs 0.0: pcmcia: could not parse base and rmask0 of CIS >eth0: 3Com 3c562, io 0x300, irq 3, hw_addr ff:ff:ff:ff:ff:ff > 32K FIFO split 3:5 Rx:Tx, auto xcvr Best Regards Komuro >Hey, > >On Sun,

Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2009-12-19 Thread Komuro
Hi, >Any chance you could bisect it further? Also, does "lspci -vvv", >"/proc/ioports" and/or "/proc/iomem" change between -git7 and -git8? > Here is the patch that introduced the problem pointed out by bisect. but this result is apparently wrong. commit 5f1586d0dd8f6eeecf6c0d35cbca6291afd6f1

Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2009-12-19 Thread Komuro
Hi, >Any chance you could bisect it further? Also, does "lspci -vvv", >"/proc/ioports" and/or "/proc/iomem" change between -git7 and -git8? Here is the difference of lspci , ioports and iomem. I tried the bisect, but I failed to get the correct result. maybe I mistyped the bisect command. (It

Re: Re: Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2009-12-18 Thread Komuro
g >>out the line "pci_set_cacheline_size(dev)" in >>drivers/pcmcia/cardbus.c:cardbus_config_irq_and_cls() ? >> > >Even if I revert the "pccard: configure CLS on attach" manually, >3com 3c562 still does not work. > >Best Regards >Komuro > > &g

Re: Re: [BUG? kernel 2.6.32-git10] 3com 3c562 multifunction card does not work

2009-12-16 Thread Komuro
5fe59c9db01692a0d pccard: configure CLS on attach > >which only seems relevant for CardBus. Nonetheless: could you try commenting >out the line "pci_set_cacheline_size(dev)" in >drivers/pcmcia/cardbus.c:cardbus_config_irq_and_cls() ? > Even if I revert the "pc

  1   2   >