https://bugzilla.kernel.org/show_bug.cgi?id=26142
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #10 from Helmut helmut.schla...@web.de ---
Great!
Tried kernel-4.0.4 and it booted without problems.
So pcmcia_rsrc.probe_io=0 is not necessary anymore.
Thanks a lot!
Helmut
--
You are receiving this mail because:
You are the
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #9 from Alan a...@lxorguk.ukuu.org.uk ---
For pure PCI I've recently submitted some proposed patches that fix a ton of
PCMCIA bugs and also add a pure PCI resource manager for more modern systems.
Might be worth giving it a spin.
Alan
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #8 from Helmut helmut.schla...@web.de ---
I unset CONFIG_PCMCIA_PROBE by editing drivers/pcmica/Kconfig for testing:
config PCMCIA_PROBE
bool
default y if ISA !ARCH_SA1100 !PARISC !PPC_BOOK3S
There's no difference
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #5 from Alan a...@lxorguk.ukuu.org.uk ---
The kernel normally considers 0 to be unallocated and 0x00-0x07 seem to be
odd addresses to be allocated for PCMCIA use. On the PC we do scan ranges
because for old style PCMCIA the PC
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #6 from Helmut helmut.schla...@web.de ---
0x00-0x07 was probably not the best example chosen, but it's also the same for
0x1200, where it eventually is inserted.
Yes, CONFIG_PCMCIA_PROBE is set.
The question is, if it should be
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #7 from Alan a...@lxorguk.ukuu.org.uk ---
It is not a platform I know well enough to be sure - but it certainly looks
like in your case at least it would be worth disabling it and checking
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #4 from Helmut helmut.schla...@web.de ---
Noticed that the module rsrc_nonstatic is since 2.6.35 called pcmcia_rsrc.
Thus, the old behaviour of kernel 2.6.33 of effectively not probing the IO
addresses can be achieved for all kernels
https://bugzilla.kernel.org/show_bug.cgi?id=26142
--- Comment #3 from Helmut helmut.schla...@web.de ---
I think I found the cause of the error: it is not caused by yenta_socket.c
itself, but in do_io_probe of rsrc_nonstatic.c, when it calls 'inb()':
2.6.33.6, line 218f:
for (i = base, most =
https://bugzilla.kernel.org/show_bug.cgi?id=26142
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Kernel Version|2.6.36.2|3.12
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=26142
Helmut helmut.schla...@web.de changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugzilla.kernel.org/show_bug.cgi?id=26142
Helmut helmut.schla...@web.de changed:
What|Removed |Added
CC||helmut.schla...@web.de
12 matches
Mail list logo
