From: Michel Salim <mas118@demeter.cs.york.ac.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Michel Salim <mas118@cs.york.ac.uk>,
LKML <linux-kernel@vger.kernel.org>,
dhinds@valinux.com
Subject: Re: i82365 PCI-PCMCIA bridge still not working in 2.4.0-test11
Date: Thu, 23 Nov 2000 01:05:16 +0000 [thread overview]
Message-ID: <3A1C6D4C.7060306@demeter.cs.york.ac.uk> (raw)
In-Reply-To: <3A1AC075.4020506@cs.york.ac.uk> <4186.974889923@redhat.com>
Thanks for the patch... but it does not quite work. It applies cleanly,
but upon booting the patched kernel, the machine freezes completely upon
PCMCIA initialisation (it got to the point where the init script said
'Loading modules' then nothing). CTRL+ALT+DEL does not work, either.
Anyone got a clue? Would love to help debug this if someone would just
walk me through it.
Michel
David Woodhouse wrote:
> mas118@cs.york.ac.uk said:
>
>> Installed kernel 2.4.0-test11 on my Debian Woody box today. Had no
>> problem apart from getting PCMCIA to work. I have a PCI-PCMCIA adapter
>> on my desktop PC, using the Cirrus Logic CL6729 chipset;
>
>
> Linus got a bit carried away when stripping out all the CardBus support
> from i82365, and took out the support for PCI-PCMCIA bridges too.
>
> Try this snapshot of my development tree, or use lspci to find the IO
> address of the device and specify that to the existing module.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 18:35 Michel Salim
2000-11-22 10:45 ` David Woodhouse
2000-11-23 1:05 ` Michel Salim [this message]
[not found] ` <11299.974975638@redhat.com>
2001-01-03 9:39 ` Michel Salim
2001-01-03 9:58 ` David Woodhouse
2001-01-05 15:32 ` Michel Salim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A1C6D4C.7060306@demeter.cs.york.ac.uk \
--to=mas118@demeter.cs.york.ac.uk \
--cc=dhinds@valinux.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mas118@cs.york.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®