From: Milan Plzik <milan.plzik@gmail.com>
To: Steven Newbury <s_j_newbury@yahoo.co.uk>
Cc: linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pxa2xx PCMCIA timing issue on iPAQ H5550
Date: Sun, 19 Aug 2007 14:03:46 +0200 [thread overview]
Message-ID: <1187525026.25210.33.camel@localhost> (raw)
In-Reply-To: <167613.90719.qm@web25003.mail.ukl.yahoo.com>
On Pi, 2007-08-17 at 00:48 +0100, Steven Newbury wrote:
> --- Milan Plzik <milan.plzik@gmail.com> wrote:
>
> > On Å t, 2007-08-09 at 16:06 +0100, Steven Newbury wrote:
> > > --- Milan Plzik <milan.plzik@gmail.com> wrote:
> > >
> > > > Good day,
> > > >
> > > > recently I've been trying to get working PCMCIA interface on H5000
> > > > ipaq series, using dual PCMCIA sleeve. So far things work correctly, but
> > > > I had to do one modification to drivers/pcmcia/pxa2xx_base.c to get the
> > > > interface working with orinoco gold PCMCIA card (wired pcnet_cs ethernet
> > > > card worked even without this modification). Patch attached.
> > > >
> > > > The issue has something to do with assert time on PCMCIA bus, but I'm
> > > > not really sure what -- I found the working value just by trial&error
> > > > approach. I'm not sure how is the assert value in pxa2xx_mcxx_asst
> > > > calculated (I know, simple formula, but the reason why is it calculated
> > > > that way is not obvious for me), neither that my modification is
> > > > correct. It just works with iPAQ.
> > > >
> > > I posted a patch to linux-arm-kernel which reworked the timing code. The
> > > existing is/was IMHO wrong and this showed up for me with frequency scaling
> > > where the code would not keep the PCMCIA timings constant with changes to
> > the
> > > core frequency. Here it is:
> > > http://marc.info/?l=linux-arm-kernel&m=116861295404294&w=2
> >
> > I found out that drivers/pcmcia/pxa2xx_base.c from handhelds.org tree
> > was a bit modified. I tried both vanilla kernel tree and vanilla+this
> > patch -- both worked with pcnet_cs, and neither one with orinoco card.
> > As far as I understand, handhelds.org modification makes use of memory
> > clock instead of cpu clock for calculations. But even when using old
> > handhelds.org driver with modified formulas, orinoco card won't
> > initialize.
> >
> What actually happens? I'm using a spectrum24 and it works fine on my Zaurus
> SL-C3100. Is it trying to load the firmware? I'm still using 2.6.20, so if
> something has broken since I don't know about it.
The orinoco_cs driver fails to initialize the card, it doesn't read
proper value from SWSUPPORT0 register (or something like that, I don't
remember exactly). Driver sets some magic value there and expects to
read it back correctly, but that doesn't happen.
>
> > I'm not really sure how things should be calculated, I'll try ask
> > folks who modified the hh.org driverto see what could cause the
> > problems.
> >
> It is all detailed in the PXA2xx manuals. I did try to enough details in my
> comments to make sense of the calculation. As was commented on when I posted
> it, it isn't ideal since it uses divides which are relatively slow on ARMs.
Err, I did not mean your code, but handhelds.org one:). I need to ask
why it has been changed to the actual state -- precisely why it doesn't
use pxa core frequency, but memclk.
>
>
> Steve
>
>
Milan
> ___________________________________________________________
> Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html
prev parent reply other threads:[~2007-08-19 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 20:22 [PATCH] pxa2xx PCMCIA timing issue on iPAQ H5550 Milan Plzik
2007-08-09 15:06 ` Steven Newbury
2007-08-16 9:28 ` Milan Plzik
2007-08-16 23:48 ` Steven Newbury
2007-08-19 12:03 ` Milan Plzik [this message]
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=1187525026.25210.33.camel@localhost \
--to=milan.plzik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=s_j_newbury@yahoo.co.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.