----- Original Message -----
> From: [email protected]
> To: "alexey kodanev" <[email protected]>
> Cc: "Jan Stancek" <[email protected]>, "vasily isaenko"
> <[email protected]>, [email protected]
> Sent: Tuesday, 11 June, 2013 2:11:06 PM
> Subject: Re: [LTP] [PATCH] fw_load: new test of device firmware loading
>
> Hi!
> > >> Right, we should at least limit the module build to kernel versions that
> > >> are known to work. In this particular case I would limit it to 3.7+
> > > Or even better to be both forward and backward compatible, we should not
> > > stop the build when kernel module has failed to build. We should carry
> > > on with the build, install etc. and return TCONF when the particula test
> > > was called.
> > >
> > As I understand from the last comment, userspace test should check
> > availability
> > of module.ko. If it didn't find the module, the test must return TCONF,
> > further, no need to check modules build against kernel version. Is it
> > correct?
>
> The insmod or modprobe will return error when you try to insert kernel
> module build against different kerenel (i.e. version magic is
> different).
>
> So I would do the logick as:
Perhaps also:
0. if module fails to build, continue with rest of LTP build
>
> 1. Is there foo.ko?
>
> if not -> module wasn't build -> TCONF
>
> 2. Try to insmod/modprobe module
>
> if failure -> most likely module not compatible with kernel -> TBROK
>
> 3. do actual test
>
> ...
>
> --
> Cyril Hrubis
> [email protected]
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
