lkml.org 
[lkml]   [2021]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 00/20] kbuild: unify the install.sh script usage
    On Wed, Apr 07, 2021 at 09:02:29AM +0100, Russell King - ARM Linux admin wrote:
    > On Wed, Apr 07, 2021 at 09:46:18AM +0200, Greg Kroah-Hartman wrote:
    > > On Wed, Apr 07, 2021 at 09:18:11AM +0200, Geert Uytterhoeven wrote:
    > > > Hi Greg,
    > > >
    > > > Thanks for your series!
    > > >
    > > > On Wed, Apr 7, 2021 at 7:34 AM Greg Kroah-Hartman
    > > > <gregkh@linuxfoundation.org> wrote:
    > > > > Almost every architecture has copied the "install.sh" script that
    > > > > originally came with i386, and modified it in very tiny ways. This
    > > > > patch series unifies all of these scripts into one single script to
    > > > > allow people to understand how to correctly install a kernel, and fixes
    > > > > up some issues regarding trying to install a kernel to a path with
    > > > > spaces in it.
    > > > >
    > > > > Note that not all architectures actually seem to have any type of way to
    > > > > install a kernel, they must rely on external scripts or tools which
    > > > > feels odd as everything should be included here in the main repository.
    > > > > I'll work on trying to figure out the missing architecture issues
    > > > > afterward.
    > > >
    > > > I'll bite ;-)
    > > >
    > > > Does anyone actually use these scripts (outside of x86)?
    >
    > Yes, every time I build a kernel. My kernel build system involves
    > typing "kbuild <flags> <dirname> <machines...>" and the kernel gets
    > built in ../build/<dirname>. When the build completes, it gets
    > installed into ~/systems/<dirname>, tar'd up, and copied to the
    > destination machines, unpacked, installed as appropriate, and
    > the machine rebooted if requested.
    >
    > The installation step is done via the ~/bin/installkernel script.

    So you don't use install.sh at all except to invoke your local script.

    > > > I assume the architectures that have them, only have them because they
    > > > were copied from x86 while doing the initial ports ("oh, a file I don't
    > > > have to modify at all.").
    > > > But installing the kernel can be very platform-specific.
    > > > Do you need the vmlinux, vmlinux.gz, Image, zImage, uImage, ...?
    > > > With separate or appended DTB?
    >
    > My scripts deal with all that.
    >
    > However, I haven't been able to review the changes that are being
    > made because I have no visibility of the common "scripts" version.
    > Provided it offers exactly the same functionality as the arm32
    > version, I'm happy. If it doesn't, it may cause a regression, and
    > I will be reporting that.

    It should be identical, if I got something wrong please let me know.

    thanks,

    greg k-h

    \
     
     \ /
      Last update: 2021-04-07 10:08    [W:2.187 / U:0.228 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site