public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: cedric_hombourger@mentor.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: Install config and map file to /boot
Date: Wed, 25 Mar 2020 00:07:12 -0700 (PDT)	[thread overview]
Message-ID: <7d0d4cc5-149e-48f9-8391-23d324df6490@googlegroups.com> (raw)
In-Reply-To: <df86ae6a-3f05-1fcc-35b3-cc696de54736@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 3174 bytes --]



On Tuesday, March 17, 2020 at 6:40:01 PM UTC+1, Jan Kiszka wrote:
>
> On 17.03.20 18:19, vijai kumar wrote: 
> > I am not sure how to test the um use case in kernel in ISAR. Are there 
> > any specific targets in ISAR that I am missing? 
> > 
>
> I don't think we had a um use case so far, so there might be things 
> silently broken. Not sure if Cedric tested the um special handling, I 
> surely didn't. 
>

used "um" for another project (and without Isar).
I would recommend we don't bother with it as far as Isar is concerned until 
we get a request for it


> Jan 
>
> > Thanks, 
> > Vijai Kumar K 
> > 
> > On Tuesday, March 17, 2020 at 10:45:13 PM UTC+5:30, vijai kumar wrote: 
> > 
> >     Align with upstream debian linux-image package. Install the config 
> and 
> >     System.map file to /boot directory. Skip installation for User Mode 
> >     Linux. 
> > 
> >     Signed-off-by: Vijai Kumar K <Vijaikumar_...@mentor.com 
> <javascript:> 
> >     <mailto:Vijaikumar_Kanagarajan@mentor.com <javascript:>>> 
> >     --- 
> >       .../linux/files/debian/isar/install.tmpl           | 14 
> >     ++++++++++++++ 
> >       1 file changed, 14 insertions(+) 
> > 
> >     diff --git 
> >     a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl 
> >     b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl 
> >     index 12d592d..4e1f850 100644 
> >     --- a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl 
> >     +++ b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl 
> >     @@ -37,6 +37,8 @@ do_install() { 
> >           set -x 
> > 
> >           install_image 
> >     +    install_config 
> >     +    install_map 
> >           install_hooks 
> >           install_dtbs 
> >           install_kmods 
> >     @@ -69,6 +71,18 @@ install_image() { 
> >           install_image_debug 
> >       } 
> > 
> >     +install_config() { 
> >     +    if [ "${ARCH}" != "um" ]; then 
> >     +        cp ${O}/.config ${deb_img_dir}/$(dirname 
> >     ${kimage_path})/config-${krel} 
> >     +    fi 
> >     +} 
> >     + 
> >     +install_map() { 
> >     +    if [ "${ARCH}" != "um" ]; then 
> >     +        cp ${O}/System.map ${deb_img_dir}/$(dirname 
> >     ${kimage_path})/System.map-${krel} 
> >     +    fi 
> >     +} 
> >     + 
> >       install_image_debug() { 
> >           # Different tools want the image in different locations 
> >           # perf 
> >     -- 
> >     2.17.1 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "isar-users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to isar-...@googlegroups.com <javascript:> 
> > <mailto:isar-users+unsubscribe@googlegroups.com <javascript:>>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/isar-users/e1c7b955-185e-4f10-83f5-349ad6847274%40googlegroups.com 
> > <
> https://groups.google.com/d/msgid/isar-users/e1c7b955-185e-4f10-83f5-349ad6847274%40googlegroups.com?utm_medium=email&utm_source=footer>. 
>
>
>
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE 
> Corporate Competence Center Embedded Linux 
>

[-- Attachment #1.2: Type: text/html, Size: 6000 bytes --]

  reply	other threads:[~2020-03-25  7:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 17:14 Vijai Kumar K
2020-03-17 17:19 ` vijai kumar
2020-03-17 17:39   ` Jan Kiszka
2020-03-25  7:07     ` cedric_hombourger [this message]
2020-04-03  7:28       ` vijai kumar
2020-04-03  7:29         ` vijai kumar
2020-03-17 17:32 ` Jan Kiszka
2020-03-18  5:53   ` vijai kumar
2020-03-18  7:34     ` Henning Schild
2020-03-18 13:03       ` vijai kumar
2020-03-18 13:21       ` [PATCH v2] " Vijai Kumar K
2020-03-23  6:12         ` Jan Kiszka
2020-03-23  6:53           ` Henning Schild
2020-03-23  6:55             ` Jan Kiszka
2020-03-23  7:49               ` vijai kumar
2020-03-23  9:13               ` Henning Schild
2020-03-23  9:24                 ` vijai kumar
2020-03-23 10:40                   ` Henning Schild
2020-03-23 13:40                     ` [PATCH v3 1/2] " Vijai Kumar K
2020-03-23 13:40                       ` [PATCH v3 2/2] meta/recipes-kernel: Replace cp with install Vijai Kumar K
2020-04-17 15:05                       ` [PATCH v3 1/2] linux-custom: Install config and map file to /boot Baurzhan Ismagulov
2020-04-17 18:44                         ` vijai kumar
2020-04-17 18:59                           ` vijai kumar
2020-04-20  9:28                             ` Baurzhan Ismagulov
2020-04-20 10:07                               ` vijai kumar
2020-04-20 16:03                                 ` Baurzhan Ismagulov
2020-04-20 19:46                                   ` Henning Schild
2020-04-20 19:51                                 ` Henning Schild

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=7d0d4cc5-149e-48f9-8391-23d324df6490@googlegroups.com \
    --to=cedric_hombourger@mentor.com \
    --cc=isar-users@googlegroups.com \
    /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