From: Russell King <rmk@arm.linux.org.uk>
To: Stefan Jones <cretin@gentoo.org>
Cc: linux-kernel@vger.kernel.org, Dominik Brodowski <linux@brodo.de>
Subject: Re: [2.6.0-test1] yenta_socket.c:yenta_get_status returns bad value compared to 2.4
Date: Sat, 2 Aug 2003 18:08:37 +0100 [thread overview]
Message-ID: <20030802180837.B1895@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1059244318.3400.17.camel@localhost>; from cretin@gentoo.org on Sat, Jul 26, 2003 at 07:31:59PM +0100
On Sat, Jul 26, 2003 at 07:31:59PM +0100, Stefan Jones wrote:
> It seems the the change from 2.4 to 2.6 made the state read from
> yenta_get_status change it's return value. It reads it from hardware.
The get_status function is called multiple times during card
initialisation. I doubt that it is valid to compare the get_status
values from 2.4 and 2.6 kernels, without examining what's going on
in the cs.c code.
It would be helpful if you could apply the patch to cs.c which I've
recently posted to lkml, and report back the full kernel messages,
including the messages you get from your printk in yenta_get_status().
The message id was: <20030802173352.A1895@flint.arm.linux.org.uk>
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-08-02 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 18:31 [2.6.0-test1] yenta_socket.c:yenta_get_status returns bad value compared to 2.4 Stefan Jones
2003-07-26 19:17 ` OSDL
2003-07-27 9:46 ` Stefan Jones
2003-08-02 17:08 ` Russell King [this message]
2003-08-03 11:07 ` Stefan Jones
2003-08-03 12:50 ` Russell King
2003-08-03 13:34 ` Stefan Jones
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=20030802180837.B1895@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cretin@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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;
as well as URLs for NNTP newsgroup(s).