From: chrubis@suse.cz
To: alexey.kodanev@oracle.com
Cc: Vasily Isaenko <vasily.isaenko@oracle.com>,
ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Device firmware loading test
Date: Thu, 30 May 2013 13:07:59 +0200 [thread overview]
Message-ID: <20130530110759.GA16265@rei.suse.cz> (raw)
In-Reply-To: <51A5E74C.5000002@oracle.com>
Hi!
> I'm developing a test of device firmware loading (after 3.7 it can be
> loaded directly or as usual), but I'm not sure under which ltp directory
> it should be placed. Is it OK if I use two locations as described below?
>
> .../testcases/kernel/device-drivers/firmware/fw_load_kernel/fw_load.ko -
> kernel space part (calls request_firmware with specified parameters), and
>
> .../testcases/kernel/device-drivers/firmware/fw_load_user/fw_load - user
> space part (creates firmware files, replaces udev's firmware searched
> paths, loads the module, prints results...).
The problem with device-drivers directory is that the code there is
broken (unmaintained since 2009 or so) and the make (from the top
directory) doesn't go there. It should be cleaned/removed/fixed but
nobody had time to look at the tests and decide what to do with them.
Otherwise the destination fits well enough.
And there is another problem with building kernel modules, I think that
we don't have any configure checks to find out if kernel-devel is
installed (i.e. /lib/modules/$(version)/build/ exists) and which kernel
version to use, etc. But this part shouldn't be that hard.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-05-30 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 12:20 [LTP] [PATCH] New core test of cgroups and extended attributes Alexey Kodanev
2013-05-28 14:37 ` chrubis
[not found] ` <51A4C663.7010506@oracle.com>
2013-05-28 15:43 ` chrubis
[not found] ` <51A5E74C.5000002@oracle.com>
2013-05-30 11:07 ` chrubis [this message]
[not found] ` <51A747E8.7070105@oracle.com>
2013-05-30 13:13 ` [LTP] Device firmware loading test chrubis
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=20130530110759.GA16265@rei.suse.cz \
--to=chrubis@suse.cz \
--cc=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@oracle.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