All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Johnny Vestergaard <jkv@unixcluster.dk>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, poky@yoctoproject.org
Subject: Re: Auto loading nls-iso8859-1kernel module
Date: Fri, 31 Oct 2014 19:50:19 +0100	[thread overview]
Message-ID: <20141031185019.GG15148@jama> (raw)
In-Reply-To: <CAO+iiFwKrRkwHj2HVjam31XSp-TXac=SGZgAh53A_FfOjYGGmg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

On Fri, Oct 31, 2014 at 04:51:26PM +0100, Johnny Vestergaard wrote:
> Still no luck, but thanks! Now i at least have a pointer to a potential
> root cause.

Is this with oe-core master or dizzy?

In that case you need to add the module basename in KERNEL_MODULE_AUTOLOAD and in
cases where module name == basename, you don't need module_autoload
variable at all.

> On Fri, Oct 31, 2014 at 3:53 PM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
> 
> > On Friday 31 October 2014 15:49:29 Johnny Vestergaard wrote:
> > > On Fri, Oct 31, 2014 at 1:11 PM, Paul Eggleton <
> > >
> > > paul.eggleton@linux.intel.com> wrote:
> > > > On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote:
> > > > > Thanks for the quick response. Actually i tried adding it to
> > local.conf,
> > > > > but it seems like bitbake did not pick it up - at least it did not
> > > >
> > > > rewrite
> > > >
> > > > > the rootfs.
> > > >
> > > > Right, that is a known issue - you'll have to clean the kernel & image
> > as
> > > > it
> > > > won't pick up changes to the module_autoload variable after the kernel
> > has
> > > > been built:
> > > >
> > > > bitbake -c clean virtual/kernel
> > > > bitbake -c clean your-imagename
> > > >
> > > > Then you should be able to build the image with the change to
> > > > module_autoload
> > > > incorporated.
> > >
> > > Thanks for the tips. certainly get's me in the right direction.
> > > But, putting the following at the end of my local.conf:
> > >
> > > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS +=  " kernel-module-nls-cp437"
> > > module_autoload_nls-cp437 = "nls-cp437"
> > >
> > > and cleaning virtual/kernel afterwards still does not autoload the
> > module -
> > > but the module is included correctly.
> >
> > Oh, sorry, I think you'd need to do:
> >
> > bitbake -c cleansstate virtual/kernel
> > bitbake -c cleansstate your-imagename
> >
> > Cheers,
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel Open Source Technology Centre
> >

> -- 
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-10-31 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 11:43 Auto loading nls-iso8859-1kernel module Johnny Vestergaard
2014-10-31 11:46 ` Paul Eggleton
2014-10-31 12:01   ` Johnny Vestergaard
2014-10-31 12:11     ` Paul Eggleton
2014-10-31 14:49       ` Johnny Vestergaard
2014-10-31 14:53         ` Paul Eggleton
2014-10-31 15:51           ` Johnny Vestergaard
2014-10-31 18:50             ` Martin Jansa [this message]
2014-10-31 23:06               ` Johnny Vestergaard

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=20141031185019.GG15148@jama \
    --to=martin.jansa@gmail.com \
    --cc=jkv@unixcluster.dk \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.