From: Ulrich Eckhardt <eckhardt@satorlaser.com>
To: linux-mips@linux-mips.org
Subject: Re: Au1000 PCMCIA broken in 2.6.20
Date: Wed, 21 Feb 2007 09:19:16 +0100 [thread overview]
Message-ID: <200702210919.16930.eckhardt@satorlaser.com> (raw)
In-Reply-To: <20070221073848.GA9822@roarinelk.homelinux.net>
On Wednesday 21 February 2007 08:38, Manuel Lauss wrote:
> PCMCIA is broken on my Au1200 platform. Seems to me that accesses to
> Attribute memory are broken; a dump of the CIS reveals the following:
>
> 1.0: ParseTuple: Bad CIS tuple
> 00000000 01 03 ff ff ff 1c 04 ff ff ff ff 18 02 ff ff 20
> 00000010 04 98 00 00 00 15 20 04 ff ff ff ff ff ff ff ff
> 00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 00000030 ff ff ff ff ff ff ff 21 02 04 01 22 02 ff ff 22
[...]
> it should look like this:
> 00000000 01 03 d9 01 ff 1c 04 03 d9 01 ff 18 02 df 01 20
> 00000010 04 98 00 00 00 15 20 04 01 54 4f 53 48 49 42 41
> 00000020 20 54 48 4e 43 46 32 35 36 4d 50 47 20 00 00 00
Can you rule out a timing problem, i.e. that the system bus is configured
correctly? The reason I ask is that some values seem to be read correctly but
others not. I seem to remember something like that keeping me busy trying to
get an Au1100 to run. Also, try a different card, too, I experienced hard
lockups with CF cards of one brand that (on an electronic level) seemed to
behave badly and cause the system to break.
> Reverting "[PATCH] Generic ioremap_page_range: mips conversion" makes it
> work again:
> http://www.linux-mips.org/git?p=linux.git;a=commitdiff_plain;h=8e087929df88
>4dbb13e383d49d192bdd6928ecbf;hp=62dfb5541a025b47df9405ff0219c7829a97d83b
I see one thing that disturbs me a lot in this code (before but even more
after this changeset): use of casts in the calls to remap_area_pages or
ioremap_page_range. Those typically only serve to hide errors and
specifically on the Au1100 (probably also on Au1200) because there the
physical addresses are 36 bit while virtual addresses are 32 bit. If there is
a truncation going on due to wrong datatypes, these casts will disable the
compiler warnings.
Apropos, the switching between 32 and 36 bit physical addresses was done via a
configuration setting in 2.4, try toggling that one, too, if it still exists.
Uli
--
Sator Laser GmbH
Geschäftsführer: Ronald Boers Steuernummer: 02/892/02900
Amtsgericht Hamburg HR B62 932 USt-Id.Nr.: DE183047360
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
next prev parent reply other threads:[~2007-02-21 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 7:38 Au1000 PCMCIA broken in 2.6.20 Manuel Lauss
2007-02-21 8:19 ` Ulrich Eckhardt [this message]
2007-02-21 8:44 ` Manuel Lauss
2007-02-21 9:37 ` Ralf Baechle
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=200702210919.16930.eckhardt@satorlaser.com \
--to=eckhardt@satorlaser.com \
--cc=linux-mips@linux-mips.org \
/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