Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #60528

Re: armel/marvell kernel size

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, 2018-03-22 at 00:12 -0300, Rogério Brito wrote:
[...]
> If nobody is working on getting a new kernel working on armel, I would
> like to (at least, unsuccessfully) try to get it to compile.
> 
> At worst, I believe, I can gain some knowledge and compare what I get from
> this armel kernel with a Kurobox HD (powerpc-based; see some notes at [0])...
> 
> [0]: http://cynic.cc/blog/posts/simple-annotations-on-compiling-a-linux-kernel-for-an-embedded-platform/
> 
> For this task, I have some questions:
> 
> 1 - To get up to speed, is there any recommended way of cross-compiling
>     the kernels, before I try it on bare-metal? When I compiled my own
>     kernels, I used to use a cross-compiler that I compiled myself and it
>     was using a very non-methodological way...

Cross-compiling works well.  For the Debian package, use:

    dpkg-buildpackage -aarmel -Pcross,pkg.linux.notools

If you want to work with the upstream source, use:

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-

[...]
> 3 - Besides the points listed above, what else can usually be disabled,
>     if they don't pertain/make sense in a system like a small armel box?

If I knew that I'd have already done it (or suggested it).

> 4 - What is the preferred tree to be used for Debian's kernel
>     development? I am used to compile kernels from Linus's git tree with no
>     patches, but I know that Debian carries a sizable amount of patches...

Clone the kernel team's git repository and use whatever upstream
version we are using.

> I may have some free time after Easter to have some trial and errors, but it
> may even be the case that some free time becomes available before that...
> 
> > We would like to ideally upload a 4.15.x based version to unstable
> > (currently imported 4.15.4).
> 
> I now see that there were some 4.16rc's uploaded to the archive... I guess
> that this is tied with my 4th point above, right?

You can work on either the sid branch (currently 4.15.y) or master 
(4.16-rcN, for experimental).  But in a few weeks 4.16 will be ready
for unstable and it will probably result in further code growth, so you
might as well work on master.

Ben.

> Hope to have some luck with my 1st armel adventures,
> 
> 
> Rogério Brito.
> 
-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-01-18 05:30 +0100
  Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-01-22 15:00 +0100
    Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-01-23 19:40 +0100
      Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-01-26 19:00 +0100
      Re: armel/marvell kernel size Salvatore Bonaccorso <carnil@debian.org> - 2018-02-17 13:50 +0100
        Re: armel/marvell kernel size Bastian Blank <waldi@debian.org> - 2018-02-17 14:20 +0100
          Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-03-22 13:00 +0100
        Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-03-22 13:00 +0100
          Re: armel/marvell kernel size Rogério Brito <rbrito@gmail.com> - 2018-03-22 19:20 +0100
        Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-23 00:10 +0100
        Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-24 03:00 +0100
          Re: armel/marvell kernel size Rogério Brito <rbrito@gmail.com> - 2018-03-27 07:50 +0200
            Re: armel/marvell kernel size Stefan Monnier <monnier@iro.umontreal.ca> - 2018-03-27 14:40 +0200
              Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 22:30 +0200
                Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-03-27 22:50 +0200
                Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 23:30 +0200
                Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-03-28 11:30 +0200
                Re: armel/marvell kernel size Federico Pietro Briata <federico@briata.org> - 2018-03-28 14:30 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-01 15:30 +0200
                Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-04-03 08:00 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-07 16:20 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-07 17:00 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-13 02:10 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-15 18:30 +0200
                Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-04-02 01:50 +0200
                Re: armel/marvell kernel size Stefan Monnier <monnier@iro.umontreal.ca> - 2018-03-27 23:30 +0200
            Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-27 21:10 +0200
              Re: armel not to be released anymore? (was: armel/marvell kernel  size) Ben Hutchings <ben@decadent.org.uk> - 2018-03-27 21:30 +0200
              armel not to be released anymore? (was: armel/marvell kernel size) "W. Martin Borgert" <debacle@debian.org> - 2018-03-27 21:40 +0200
                Re: armel not to be released anymore? (was: armel/marvell kernel size) Paul Wise <pabs@debian.org> - 2018-03-28 06:40 +0200
              Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 22:50 +0200

csiph-web