From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM Linux Kernel Update
Date: Fri, 13 Nov 2015 10:40:29 +0100 [thread overview]
Message-ID: <9020659.GYXS8BbG6X@wuerfel> (raw)
In-Reply-To: <CAMu38xLbRcOfdGLF+ozMA7G-tqzqykvsaDToY43sdMO4FP4b5w@mail.gmail.com>
On Thursday 12 November 2015 22:43:53 Albino B Neto wrote:
> 2015-11-12 21:46 GMT-02:00 Satay Epic <satayepic@gmail.com>:
> > Hello,
> >
> > I've an ARM SL3516 board with Linux 2.6.15 and I've tool-chain setup.
> > I could able to compile the GPL source. This board has red-boot.
> >
> > I would like to update the kernel to 3.8.24. My first attempt so not
> > sure about anything I should know, gotchas etc.
> >
> > Any advice about the compilation , config will be appreciated.
3.8.24 is also really old already, try going to 4.1 or 4.3 right away,
and submit any patches that you might need for integration into
mainline Linux once you are done.
See http://git.openwrt.org/?p=openwrt.git;a=tree;f=target/linux/gemini;h=b74c3d8f0100e2ac8a4d71c4d23c082db2993e63;hb=HEAD
for a tree that has some of the missing parts for gemini, including a
config and some drivers that might be helpful. This is based on 4.1
and should be easy enough to forward-port to 4.3 if you want.
> > I tried using the existing ".config" but not sure some SL3512
> > specific options would work?
Start with the config-4.1 file from openwrt.
> > Looking at the distribution, I don't see the "mach-sl2312" listed.
> > Can you just copy it from the old distribution and does it work this
> > way?
> >
> > There is this "mach-gemini" but it seems only for some W boards.
mach-gemini is what you want.
Arnd
next prev parent reply other threads:[~2015-11-13 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADohWC9sCwFbhtryZi-EbOvcBayh_6O2bEjzFaLMxHYXYBEhQg@mail.gmail.com>
2015-11-13 0:43 ` ARM Linux Kernel Update Albino B Neto
2015-11-13 1:07 ` Satay Epic
2015-11-13 9:40 ` Arnd Bergmann [this message]
2015-11-14 19:57 ` Satay Epic
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=9020659.GYXS8BbG6X@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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