From: "Stefan Lehner" <stefan-lehner@aon.at>
To: <linux-arm-kernel@lists.infradead.org>
Cc: 'Russell King - ARM Linux admin' <linux@armlinux.org.uk>
Subject: AW: StrongARM SA-1110 / SA-1111 and Kernel 4.9.210 (Jornada 720)
Date: Thu, 23 Jan 2020 17:24:55 +0100 [thread overview]
Message-ID: <000001d5d209$a7540e20$f5fc2a60$@at> (raw)
In-Reply-To: <20200122102514.GM25745@shell.armlinux.org.uk>
Hi!
Yes we can make some tests. I simply commented it out because i thought that
the kernel doesnt need it ...
If i have time i will try it with both options enabled.
Regards
Stefan
-----Ursprüngliche Nachricht-----
Von: linux-arm-kernel [mailto:linux-arm-kernel-bounces@lists.infradead.org]
Im Auftrag von Russell King - ARM Linux admin
Gesendet: Mittwoch, 22. Jänner 2020 11:25
An: Stefan Lehner
Cc: linux-arm-kernel@lists.infradead.org
Betreff: Re: StrongARM SA-1110 / SA-1111 and Kernel 4.9.210 (Jornada 720)
On Wed, Jan 22, 2020 at 11:21:36AM +0100, Stefan Lehner wrote:
>
> On Wed, Jan 22, 2020 at 09:10:13AM +0100, Stefan Lehner wrote:
> > Hi!
> > I like to get a newer Linux Kernel running on my Jornada 720. It has a
> > StrongArm SA-1110 CPU and the SA-1111 companion chip.
> > I patched the kernel source with the BX emulation to run a newer Debian
> > userland. The kernel compiled fine.
> > It starts to boot on the Jornada with the linexec bootloader. But it
seems
> > that it doesnt detect any CF or PCMCIA card. I managed to get the
> > jornada720_pcmcia_configure_socket() running and it detects the card and
> > powers it up with the correct voltage (3V for the CF card in socket 1).
>
> >> What was required for that?
>
> I had to comment out:
> # CONFIG_PCMCIA_SA1100 is not set
> and activate:
> CONFIG_PCMCIA_SA1111=y
> in the kernel .config.
Yes, you'll need CONFIG_PCMCIA_SA1111 set, because the Jornada720 uses
the companion chip. CONFIG_PCMCIA_SA1100 should make no difference, so
can we spend some time working out why you needed to disable it?
Did you get any error messages during boot with both enabled?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps
up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-23 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 8:10 StrongARM SA-1110 / SA-1111 and Kernel 4.9.210 (Jornada 720) Stefan Lehner
2020-01-22 9:22 ` Russell King - ARM Linux admin
2020-01-22 10:21 ` Stefan Lehner
2020-01-22 10:25 ` Russell King - ARM Linux admin
2020-01-23 16:24 ` Stefan Lehner [this message]
2020-02-07 11:51 ` AW: " Stefan Lehner
2020-02-07 23:19 ` Russell King - ARM Linux admin
2020-02-08 7:54 ` AW: " Stefan Lehner
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='000001d5d209$a7540e20$f5fc2a60$@at' \
--to=stefan-lehner@aon.at \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.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;
as well as URLs for NNTP newsgroup(s).