Re: [yocto] qemu boot fail(root-nfs: unknown option: mountprog=21111)

2011-09-08 Thread Bruce Ashfield 
On 11-09-08 01:49 AM, 蔡振军 wrote:
> Hi ALL
> 
> QEMU run well with a pre-build kernel image from yocto site. Now just 
> change the kernel to one built myself, some error information appeared 
> about nfs. My kernel image version is 2.6.35 configured by 
> versatile_defconfig. Error information as following:
> 
> “root-nfs: unknown option: mountprog=2”,this message search nothing 
> on google.
> 
> Is there something wrong with .config? Add normally is there some 
> special configuration I should do with kernel to fit QEMU

You can't change out the kernel version / tree and expect to use the full
functionality provided by the linux-yocto kernel. In this case there are
changes to NFS and rpc to support alternate rpc ports being used to support
usermode NFS. You would need to port and test the patches for this
which can be found on yocto/standard/base

Cheers,

Bruce

> 
> Best regards
> 
> Feye
> 
> 蔡振军
> 
> 网新技术有限公司物联网事业部
> 
> 杭州天目山路226号网新大厦
> 
> 电话-138 6745 1910
> 
> 
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] qemu boot fail(root-nfs: unknown option: mountprog=21111)

2011-09-08 Thread Scott Garman 
On 09/07/2011 10:49 PM, 蔡振军 wrote:
> Hi ALL
> 
> QEMU run well with a pre-build kernel image from yocto site. Now just 
> change the kernel to one built myself, some error information appeared 
> about nfs. My kernel image version is 2.6.35 configured by 
> versatile_defconfig. Error information as following:
> 
> “root-nfs: unknown option: mountprog=2”,this message search nothing 
> on google.
> 
> Is there something wrong with .config? Add normally is there some 
> special configuration I should do with kernel to fit QEMU?

Hi Feye,

The linux-yocto kernel has patches in it to enable booting via a
userspace NFS server, which needs to use high port numbers for its
mountd and nfsd daemons. You will need to include these patches in your
custom kernel if you wish to continue using our userspace NFS boot method.

Bruce, can you point Feye to this patchset?

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] qemu boot fail(root-nfs: unknown option: mountprog=21111)

2011-09-08 Thread Bruce Ashfield 
On 11-09-08 11:09 AM, Scott Garman wrote:
> On 09/07/2011 10:49 PM, 蔡振军 wrote:
>> Hi ALL
>>
>> QEMU run well with a pre-build kernel image from yocto site. Now just
>> change the kernel to one built myself, some error information appeared
>> about nfs. My kernel image version is 2.6.35 configured by
>> versatile_defconfig. Error information as following:
>>
>> “root-nfs: unknown option: mountprog=2”,this message search nothing
>> on google.
>>
>> Is there something wrong with .config? Add normally is there some
>> special configuration I should do with kernel to fit QEMU?
> 
> Hi Feye,
> 
> The linux-yocto kernel has patches in it to enable booting via a
> userspace NFS server, which needs to use high port numbers for its
> mountd and nfsd daemons. You will need to include these patches in your
> custom kernel if you wish to continue using our userspace NFS boot method.

I already replied to this last night:

"You can't change out the kernel version / tree and expect to use the full
functionality provided by the linux-yocto kernel. In this case there are
changes to NFS and rpc to support alternate rpc ports being used to support
usermode NFS. You would need to port and test the patches for this
which can be found on yocto/standard/base"

Cheers,

Bruce

"

> 
> Bruce, can you point Feye to this patchset?
> 
> Scott
> 

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto 1.1 Beta Questions

2011-09-08 Thread Darren Hart 
On 09/07/2011 05:41 AM, Jason Kridner wrote:
> Isn't bitbake supposed to be smart enough to discover and use 'screen'
> instead now?

It depends on your setting in local.conf

TERMCMD = "${SCREEN_TERMCMD}"
TERMCMDRUN = "${SCREEN_TERMCMDRUN}"


--
Darren

> 
> On Tue, Sep 6, 2011 at 9:07 PM, Stewart, David C
>  wrote:
>> Yeah, I ran into the same thing, Brian. Installing xterm is missing from the
>> quickstart and the beta instructions. Sorry about that.
>>
>>
>> Sent from my Blackberry
>>
>> From: Brian Duffy [mailto:brdu...@gmail.com]
>> Sent: Tuesday, September 06, 2011 04:51 PM
>> To: Osier-mixon, Jeffrey; yocto@yoctoproject.org 
>> Subject: Re: [yocto] Yocto 1.1 Beta Questions
>>
>> Okay, so it turns out that I had already downloaded what I needed with the
>> instructions from the latest blog post for the beta release. It specifically
>> mentions certain command to replace from the quick start guide. So I went
>> into the "oe-beta" directory and ran . ./oe-init-build-env ~/my-build and
>> that set up my environment variables. When I ran bitbake core-image-minimal
>> I got an error stating that xterm was not installed. That might be something
>> to include in the quick start section of things to install first. Anyway, it
>> seems to be happily building a minimal linux distro for the emulator to run.
>> I'll let you know if it works out.
>> thnx
>> Brian
>>
>> On Tue, Sep 6, 2011 at 3:28 PM, Osier-mixon, Jeffrey
>>  wrote:
>>>
>>> One more thing - if you prefer a tarball to git (easier on some corporate
>>> networks) the process is the same, just un-tar the tarball into a working
>>> directory and cd into the poky subdir and go from there. The tarball should
>>> be the latest stable release.
>>>
>>> On Tue, Sep 6, 2011 at 12:27 PM, Osier-mixon, Jeffrey
>>>  wrote:

 Hi Brian, sorry for the delay.
 If you download the poky tarball or use git to grab it and then follow
 the instructions on the quick-start, the tools should build automatically.
  In a nutshell, try this:
 git clone git://git.yoctoproject.org/poky.git
 cd poky
 . ./oe-core-build-env
 [that should put you into a build directory]
 vi conf/local.conf  [set at least MACHINE, instructions in the file]
 bitbake core-minimal
 I hope this helps!  I'm on IRC as Jefro or available by email, let me
 know if I can help at all.

 On Sat, Sep 3, 2011 at 5:52 PM, Brian Duffy  wrote:
>
> Thanks for the input Jeff. I have not downloaded the tools yet. I'll
> probably download the tarball since I don't have much experience with git.
> I'll set the bbpath in local.conf and uninstall bitbake from the package
> manager before I do so. I guess building the tools will take care of 
> bitbake
> and pseudo. Any help with how to build the tools would be appreciated, but
> no hurry, enjoy the holiday!
> thnx
> Brian
>
> On Sat, Sep 3, 2011 at 5:50 PM, Osier-mixon, Jeffrey
>  wrote:
>>
>> Hi Brian - both bitbake and pseudo are part of the Yocto toolset. The
>> standard bitbake from the package manager on your host is not the correct
>> one. Make sure you have set your environment properly by sourcing the
>> build-env script, and it should be set correctly.
>> As Jason says, set BBPATH in your project directory in conf/local.conf
>> How did you download the tools, tarball or git?  I find it easiest to
>> do this:
>> git clone git://git.yoctoproject.org/poky.git
>> Note that responses may be delayed on a US holiday weekend :)
>> On Sat, Sep 3, 2011 at 1:48 PM, Jason Kridner
>>  wrote:
>>>
>>> On Sat, Sep 3, 2011 at 2:43 PM, Brian Duffy  wrote:
 Hi Yocto group. I am new to Yocto. I followed the starters guide and
 When
 running bitbake I get some errors. first it complains that pseudo is
 not
 available but required, and then it complains that bbpath is not
 set. What
 is pseudo?
>>>
>>> Google should have helped you with this question:
>>> http://www.yoctoproject.org/projects/pseudo.
>>>
>>> I believe the primary purpose is to be able to create files with root
>>> ownership without root access.  This is critical for building your
>>> file system.
>>>
 I have sudo installed and setup to work for me, but I don't know
 what pseudo is. Also, bitbake was not installed on my fresh install
 of
 Fedora 15 so I installed it through the package manager.
>>>
>>> I doubt you want to do that, but I don't see anything in the
>>> instructions provided to tell you where to get it either.
>>>
 I guess that was
 not included in the packages from the getting started guide. Where
 do I set
 the bbpath?
>>>
>>> Did you edit conf/local.conf?
>>>
 I followed the getting started guide and replaced the
 appropriate commands with the ones

Re: [yocto] Yocto 1.1 Beta Questions

2011-09-08 Thread Saul Wold 

On 09/08/2011 09:20 AM, Darren Hart wrote:

On 09/07/2011 05:41 AM, Jason Kridner wrote:

Isn't bitbake supposed to be smart enough to discover and use 'screen'
instead now?


It depends on your setting in local.conf

TERMCMD = "${SCREEN_TERMCMD}"
TERMCMDRUN = "${SCREEN_TERMCMDRUN}"

Actually for devshell I think it's OE_TERMINAL="screen", Chris L. was 
going to do a write up on this I think


Sau!



--
Darren



On Tue, Sep 6, 2011 at 9:07 PM, Stewart, David C
  wrote:

Yeah, I ran into the same thing, Brian. Installing xterm is missing from the
quickstart and the beta instructions. Sorry about that.


Sent from my Blackberry

From: Brian Duffy [mailto:brdu...@gmail.com]
Sent: Tuesday, September 06, 2011 04:51 PM
To: Osier-mixon, Jeffrey; yocto@yoctoproject.org
Subject: Re: [yocto] Yocto 1.1 Beta Questions

Okay, so it turns out that I had already downloaded what I needed with the
instructions from the latest blog post for the beta release. It specifically
mentions certain command to replace from the quick start guide. So I went
into the "oe-beta" directory and ran . ./oe-init-build-env ~/my-build and
that set up my environment variables. When I ran bitbake core-image-minimal
I got an error stating that xterm was not installed. That might be something
to include in the quick start section of things to install first. Anyway, it
seems to be happily building a minimal linux distro for the emulator to run.
I'll let you know if it works out.
thnx
Brian

On Tue, Sep 6, 2011 at 3:28 PM, Osier-mixon, Jeffrey
  wrote:


One more thing - if you prefer a tarball to git (easier on some corporate
networks) the process is the same, just un-tar the tarball into a working
directory and cd into the poky subdir and go from there. The tarball should
be the latest stable release.

On Tue, Sep 6, 2011 at 12:27 PM, Osier-mixon, Jeffrey
  wrote:


Hi Brian, sorry for the delay.
If you download the poky tarball or use git to grab it and then follow
the instructions on the quick-start, the tools should build automatically.
  In a nutshell, try this:
git clone git://git.yoctoproject.org/poky.git
cd poky
. ./oe-core-build-env
[that should put you into a build directory]
vi conf/local.conf  [set at least MACHINE, instructions in the file]
bitbake core-minimal
I hope this helps!  I'm on IRC as Jefro or available by email, let me
know if I can help at all.

On Sat, Sep 3, 2011 at 5:52 PM, Brian Duffy  wrote:


Thanks for the input Jeff. I have not downloaded the tools yet. I'll
probably download the tarball since I don't have much experience with git.
I'll set the bbpath in local.conf and uninstall bitbake from the package
manager before I do so. I guess building the tools will take care of bitbake
and pseudo. Any help with how to build the tools would be appreciated, but
no hurry, enjoy the holiday!
thnx
Brian

On Sat, Sep 3, 2011 at 5:50 PM, Osier-mixon, Jeffrey
  wrote:


Hi Brian - both bitbake and pseudo are part of the Yocto toolset. The
standard bitbake from the package manager on your host is not the correct
one. Make sure you have set your environment properly by sourcing the
build-env script, and it should be set correctly.
As Jason says, set BBPATH in your project directory in conf/local.conf
How did you download the tools, tarball or git?  I find it easiest to
do this:
git clone git://git.yoctoproject.org/poky.git
Note that responses may be delayed on a US holiday weekend :)
On Sat, Sep 3, 2011 at 1:48 PM, Jason Kridner
  wrote:


On Sat, Sep 3, 2011 at 2:43 PM, Brian Duffy  wrote:

Hi Yocto group. I am new to Yocto. I followed the starters guide and
When
running bitbake I get some errors. first it complains that pseudo is
not
available but required, and then it complains that bbpath is not
set. What
is pseudo?


Google should have helped you with this question:
http://www.yoctoproject.org/projects/pseudo.

I believe the primary purpose is to be able to create files with root
ownership without root access.  This is critical for building your
file system.


I have sudo installed and setup to work for me, but I don't know
what pseudo is. Also, bitbake was not installed on my fresh install
of
Fedora 15 so I installed it through the package manager.


I doubt you want to do that, but I don't see anything in the
instructions provided to tell you where to get it either.


I guess that was
not included in the packages from the getting started guide. Where
do I set
the bbpath?


Did you edit conf/local.conf?


I followed the getting started guide and replaced the
appropriate commands with the ones from Davids blog post for the
latest
release.

thnx
Brian
--
Duff

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yocto

Re: [yocto] Yocto 1.1 Beta Questions

2011-09-08 Thread Darren Hart 
On 09/08/2011 09:21 AM, Saul Wold wrote:
> On 09/08/2011 09:20 AM, Darren Hart wrote:
>> On 09/07/2011 05:41 AM, Jason Kridner wrote:
>>> Isn't bitbake supposed to be smart enough to discover and use 'screen'
>>> instead now?
>>
>> It depends on your setting in local.conf
>>
>> TERMCMD = "${SCREEN_TERMCMD}"
>> TERMCMDRUN = "${SCREEN_TERMCMDRUN}"
>>
> Actually for devshell I think it's OE_TERMINAL="screen", Chris L. was 
> going to do a write up on this I think

Ah, sorry, I missed that bit of context.

--
Darren

> 
> Sau!
> 
>>
>> --
>> Darren
>>
>>>
>>> On Tue, Sep 6, 2011 at 9:07 PM, Stewart, David C
>>>   wrote:
 Yeah, I ran into the same thing, Brian. Installing xterm is missing from 
 the
 quickstart and the beta instructions. Sorry about that.


 Sent from my Blackberry

 From: Brian Duffy [mailto:brdu...@gmail.com]
 Sent: Tuesday, September 06, 2011 04:51 PM
 To: Osier-mixon, Jeffrey; yocto@yoctoproject.org
 Subject: Re: [yocto] Yocto 1.1 Beta Questions

 Okay, so it turns out that I had already downloaded what I needed with the
 instructions from the latest blog post for the beta release. It 
 specifically
 mentions certain command to replace from the quick start guide. So I went
 into the "oe-beta" directory and ran . ./oe-init-build-env ~/my-build and
 that set up my environment variables. When I ran bitbake core-image-minimal
 I got an error stating that xterm was not installed. That might be 
 something
 to include in the quick start section of things to install first. Anyway, 
 it
 seems to be happily building a minimal linux distro for the emulator to 
 run.
 I'll let you know if it works out.
 thnx
 Brian

 On Tue, Sep 6, 2011 at 3:28 PM, Osier-mixon, Jeffrey
   wrote:
>
> One more thing - if you prefer a tarball to git (easier on some corporate
> networks) the process is the same, just un-tar the tarball into a working
> directory and cd into the poky subdir and go from there. The tarball 
> should
> be the latest stable release.
>
> On Tue, Sep 6, 2011 at 12:27 PM, Osier-mixon, Jeffrey
>   wrote:
>>
>> Hi Brian, sorry for the delay.
>> If you download the poky tarball or use git to grab it and then follow
>> the instructions on the quick-start, the tools should build 
>> automatically.
>>   In a nutshell, try this:
>> git clone git://git.yoctoproject.org/poky.git
>> cd poky
>> . ./oe-core-build-env
>> [that should put you into a build directory]
>> vi conf/local.conf  [set at least MACHINE, instructions in the file]
>> bitbake core-minimal
>> I hope this helps!  I'm on IRC as Jefro or available by email, let me
>> know if I can help at all.
>>
>> On Sat, Sep 3, 2011 at 5:52 PM, Brian Duffy  wrote:
>>>
>>> Thanks for the input Jeff. I have not downloaded the tools yet. I'll
>>> probably download the tarball since I don't have much experience with 
>>> git.
>>> I'll set the bbpath in local.conf and uninstall bitbake from the package
>>> manager before I do so. I guess building the tools will take care of 
>>> bitbake
>>> and pseudo. Any help with how to build the tools would be appreciated, 
>>> but
>>> no hurry, enjoy the holiday!
>>> thnx
>>> Brian
>>>
>>> On Sat, Sep 3, 2011 at 5:50 PM, Osier-mixon, Jeffrey
>>>   wrote:

 Hi Brian - both bitbake and pseudo are part of the Yocto toolset. The
 standard bitbake from the package manager on your host is not the 
 correct
 one. Make sure you have set your environment properly by sourcing the
 build-env script, and it should be set correctly.
 As Jason says, set BBPATH in your project directory in conf/local.conf
 How did you download the tools, tarball or git?  I find it easiest to
 do this:
 git clone git://git.yoctoproject.org/poky.git
 Note that responses may be delayed on a US holiday weekend :)
 On Sat, Sep 3, 2011 at 1:48 PM, Jason Kridner
   wrote:
>
> On Sat, Sep 3, 2011 at 2:43 PM, Brian Duffy  wrote:
>> Hi Yocto group. I am new to Yocto. I followed the starters guide and
>> When
>> running bitbake I get some errors. first it complains that pseudo is
>> not
>> available but required, and then it complains that bbpath is not
>> set. What
>> is pseudo?
>
> Google should have helped you with this question:
> http://www.yoctoproject.org/projects/pseudo.
>
> I believe the primary purpose is to be able to create files with root
> ownership without root access.  This is critical for building your
> file system.
>
>> I have sudo installed and setup to work for me, but I don't know
>> what pseudo is. Also, bitbake was

[yocto] [PATCH 0/2] More fixes for bug 1428

2011-09-08 Thread tom . zanussi 
From: Tom Zanussi 

oe-core commit dc3a8274c7e935fa564eea142d2535c9bcf2b272 for YOCTO #1428
broke meta-intel x86_64 builds:

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'initramfs-live-install' (but 
/usr/local/src/yocto/sugarbay/meta/recipes-core/images/core-image-minimal-initramfs.bb
 RDEPENDS on or otherwise requires it)
ERROR: initramfs-live-install was skipped: incompatible with host 
x86_64-poky-linux

This patchset restores the build.

Build and install-tested on sugarbay and crownbay.

More fixes for [YOCTO #1428]

The following changes since commit b86f811663d834064af1e6778c408eb904fad0b9:
  Darren Hart (1):
n450: update linux-yocto PREFERRED_VERSION to 3.0%

are available in the git repository at:

  git://git.yoctoproject.org/meta-intel.git tzanussi/1428-fix
  http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/1428-fix

Tom Zanussi (2):
  meta-intel/common: create a grub2 version initramfs-live-install
  meta-intel/common: remove initramfs-live-install 1.0 bbappend

 .../initramfs-live-install_1.0.bbappend|2 -
 .../initrdscripts/initramfs-live-install_2.0.bb|   24 
 2 files changed, 24 insertions(+), 2 deletions(-)
 delete mode 100644 
common/recipes-core/initrdscripts/initramfs-live-install_1.0.bbappend
 create mode 100644 
common/recipes-core/initrdscripts/initramfs-live-install_2.0.bb

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/2] meta-intel/common: create a grub2 version initramfs-live-install

2011-09-08 Thread tom . zanussi 
From: Tom Zanussi 

x86_64 compatibility was removed from the oe-core
initramfs-live-install because it didn't work well with grub 0.97.
The meta-intel x86-64 machines still need to use
initramfs-live-install so we need an x86_64-compatible recipe.

More fixes for [YOCTO #1428].

Signed-off-by: Tom Zanussi 
---
 .../initrdscripts/initramfs-live-install_2.0.bb|   24 
 1 files changed, 24 insertions(+), 0 deletions(-)
 create mode 100644 
common/recipes-core/initrdscripts/initramfs-live-install_2.0.bb

diff --git a/common/recipes-core/initrdscripts/initramfs-live-install_2.0.bb 
b/common/recipes-core/initrdscripts/initramfs-live-install_2.0.bb
new file mode 100644
index 000..da8a64d
--- /dev/null
+++ b/common/recipes-core/initrdscripts/initramfs-live-install_2.0.bb
@@ -0,0 +1,24 @@
+DESCRIPTION = "A live image init script"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+SRC_URI = "file://init-install.sh"
+
+PR = "r0"
+
+RDEPENDS="grub parted e2fsprogs-mke2fs"
+
+do_install() {
+install -m 0755 ${WORKDIR}/init-install.sh ${D}/install.sh
+}
+
+# While this package maybe an allarch due to it being a 
+# simple script, reality is that it is Host specific based
+# on the COMPATIBLE_HOST below, which needs to take precedence
+#inherit allarch
+INHIBIT_DEFAULT_DEPS = "1"
+
+FILES_${PN} = " /install.sh "
+
+# Alternatives to grub need adding for other arch support
+# consistent with grub 1.98 (grub 2)
+COMPATIBLE_HOST = "x86_64.*-linux"
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/2] meta-intel/common: remove initramfs-live-install 1.0 bbappend

2011-09-08 Thread tom . zanussi 
From: Tom Zanussi 

We can no longer use the 1.0 version of initramfs-live-install, so
remove the corresponding .bbappend.

Signed-off-by: Tom Zanussi 
---
 .../initramfs-live-install_1.0.bbappend|2 --
 1 files changed, 0 insertions(+), 2 deletions(-)
 delete mode 100644 
common/recipes-core/initrdscripts/initramfs-live-install_1.0.bbappend

diff --git 
a/common/recipes-core/initrdscripts/initramfs-live-install_1.0.bbappend 
b/common/recipes-core/initrdscripts/initramfs-live-install_1.0.bbappend
deleted file mode 100644
index d3420e0..000
--- a/common/recipes-core/initrdscripts/initramfs-live-install_1.0.bbappend
+++ /dev/null
@@ -1,2 +0,0 @@
-THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
-FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 0/2] [KERNEL] Cover letter for seperating 10/100 LAN feature from 1G and 10G

2011-09-08 Thread Saxena, Rahul 

Cover letter for separating 10/100 LAN feature from 1G and 10G. Typically a 
machine does not need both of 10/100 and 1G/10G drivers.

Signed-off-by: Rahul Saxena

Rahul Saxena (2):
  Remove 10/100 LAN support. 10/100 LAN will be configured by seperate
files
  Added seperate feature for 10/100 LAN support

 .../features/intel-e1/intel-e100.cfg   |2 ++
 .../features/intel-e1/intel-e100.scc   |1 +
 .../features/intel-e1/intel-e1.cfg |1 -
 3 files changed, 3 insertions(+), 1 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/2] [KERNEL] Remove 10/100 LAN support. 10/100 LAN will be configured by separate files

2011-09-08 Thread Saxena, Rahul 
Remove 10/100 LAN support. 10/100 LAN will be configured by separate files
Signed-off-by: Rahul Saxena

---
 .../features/intel-e1/intel-e1.cfg |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg 
b/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg
index ea9f7e9..34af860 100644
--- a/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg
+++ b/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg
@@ -1,4 +1,3 @@
 CONFIG_NETDEV_1000=y
-CONFIG_E100=y
 CONFIG_E1000E=y
 CONFIG_E1000=y
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/2] [KERNEL] Add separate feature for 10/100 LAN support

2011-09-08 Thread Saxena, Rahul 
Added separate feature for 10/100 LAN support.
Signed-off-by: Rahul Saxena

---
 .../features/intel-e1/intel-e100.cfg   |2 ++
 .../features/intel-e1/intel-e100.scc   |1 +
 2 files changed, 3 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc

diff --git a/meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg 
b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
new file mode 100644
index 000..65c96d9
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
@@ -0,0 +1,2 @@
+CONFIG_NET_PCI=y
+CONFIG_E100=y
diff --git a/meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc 
b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc
new file mode 100644
index 000..f21b629
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc
@@ -0,0 +1 @@
+kconf hardware intel-e100.cfg
--
1.7.0.4



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/2] [KERNEL] Cover letter for seperating 10/100 LAN feature from 1G and 10G

2011-09-08 Thread Bruce Ashfield 

On 11-09-08 06:05 PM, Saxena, Rahul wrote:

Cover letter for separating 10/100 LAN feature from 1G and 10G.
Typically a machine does not need both of 10/100 and 1G/10G drivers.


The change looks fine, and I'd agree that this is a useful split.
BUT (there's always a but), there are a set of boards that are currently
including the e1 feature that would currently be getting the e100,
and they'll no longer have it.

./bsp/common-pc/common-pc.scc:include features/intel-e1/intel-e1.scc
./bsp/fri2/fri2.scc:include features/intel-e1/intel-e1.scc
./bsp/fishriver/fishriver.scc:include features/intel-e1/intel-e1.scc
./bsp/romley/romley.scc:include features/intel-e1/intel-e1.scc
./bsp/emenlow/emenlow.scc:include features/intel-e1/intel-e1.scc
./bsp/crownbay/crownbay.scc:include features/intel-e1/intel-e1.scc
./bsp/common-pc-64/common-pc-64.scc:include 
features/intel-e1/intel-e1.scc


In particular the common-pc really does want that config (for qemu).
So we should do the split, but also update all those boards to include
your new feature as part of this change.

Can you try and resend with that addition ? You don't need to built/boot,
just make the touches to the files listed above and I can take care of
the rest.

Bruce



Signed-off-by: Rahul Saxena

Rahul Saxena (2):

Remove 10/100 LAN support. 10/100 LAN will be configured by seperate

files

Added seperate feature for 10/100 LAN support

.../features/intel-e1/intel-e100.cfg | 2 ++

.../features/intel-e1/intel-e100.scc | 1 +

.../features/intel-e1/intel-e1.cfg | 1 -

3 files changed, 3 insertions(+), 1 deletions(-)

create mode 100644
meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg

create mode 100644
meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 0/3] [KERNEL] Cover letter for seperating 10/100 LAN feature from 1G and 10G

2011-09-08 Thread Saxena, Rahul 
Cover letter for separating 10/100 LAN feature from 1G and 10G. Typically a 
machine does not need both of 10/100 and 1G/10G drivers.

Signed-off-by: Rahul saxenarahul.sax...@intel.com

Rahul Saxena (3):
  Remove 10/100 LAN support. 10/100 LAN will be configured by seperate
files
  Added seperate feature for 10/100 LAN support
  Added e100 feature configuration to remaining boards

 .../kernel-cache/bsp/common-pc-64/common-pc-64.scc |1 +
 meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc  |1 +
 meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc|1 +
 meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc  |2 +-
 meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc  |1 +
 meta/cfg/kernel-cache/bsp/fri2/fri2.scc|1 +
 meta/cfg/kernel-cache/bsp/romley/romley.scc|1 +
 .../features/intel-e1/intel-e100.cfg   |2 ++
 .../features/intel-e1/intel-e100.scc   |1 +
 .../features/intel-e1/intel-e1.cfg |1 -
 10 files changed, 10 insertions(+), 2 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/3] [KERNEL] Remove 10/100 LAN support. 10/100 LAN will be configured by separate files

2011-09-08 Thread Saxena, Rahul 
Remove 10/100 LAN support. 10/100 LAN will be configured by separate files
Signed-off-by: Rahul saxenarahul.sax...@intel.com

---
 .../features/intel-e1/intel-e1.cfg |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg 
b/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg
index ea9f7e9..34af860 100644
--- a/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg
+++ b/meta/cfg/kernel-cache/features/intel-e1/intel-e1.cfg
@@ -1,4 +1,3 @@
 CONFIG_NETDEV_1000=y
-CONFIG_E100=y
 CONFIG_E1000E=y
 CONFIG_E1000=y
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/3] [KERNEL] Add separate feature for 10/100 LAN support

2011-09-08 Thread Saxena, Rahul 
Added separate feature for 10/100 LAN support.
Signed-off-by: Rahul 
Saxenamailto:rahul.sax...@intel.com>>

---
 .../features/intel-e1/intel-e100.cfg   |2 ++
 .../features/intel-e1/intel-e100.scc   |1 +
 2 files changed, 3 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
 create mode 100644 meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc

diff --git a/meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg 
b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
new file mode 100644
index 000..65c96d9
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.cfg
@@ -0,0 +1,2 @@
+CONFIG_NET_PCI=y
+CONFIG_E100=y
diff --git a/meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc 
b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc
new file mode 100644
index 000..f21b629
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/intel-e1/intel-e100.scc
@@ -0,0 +1 @@
+kconf hardware intel-e100.cfg
--

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 3/3] [KERNEL] Add e100 feature configuration to all boards

2011-09-08 Thread Saxena, Rahul 
Added separate feature for 10/100 LAN support.
Signed-off-by: Rahul 
Saxenamailto:rahul.sax...@intel.com>>

---
 .../kernel-cache/bsp/common-pc-64/common-pc-64.scc |1 +
 meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc  |1 +
 meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc|1 +
 meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc  |2 +-
 meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc  |1 +
 meta/cfg/kernel-cache/bsp/fri2/fri2.scc|1 +
 meta/cfg/kernel-cache/bsp/romley/romley.scc|1 +
 7 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc 
b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
index 58dab18..a7f6cff 100644
--- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
+++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
@@ -3,6 +3,7 @@ kconf hardware common-pc-64-graphics.cfg

 include features/hpet/hpet.scc
 include features/igb/igb.scc
+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc

 include features/latencytop/latencytop.scc
diff --git a/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc 
b/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc
index d7dda80..77c3d26 100644
--- a/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc
+++ b/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc
@@ -1,6 +1,7 @@
 kconf hardware common-pc.cfg
 kconf hardware common-pc-gfx.cfg

+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc
 include features/latencytop/latencytop.scc
 include features/profiling/profiling.scc
diff --git a/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc 
b/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc
index c7cd538..63b7ad6 100644
--- a/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc
+++ b/meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc
@@ -3,6 +3,7 @@ kconf hardware crownbay.cfg
 git merge yocto/emgd

 include features/eg20t/eg20t.scc
+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc
 include features/drm-emgd/drm-emgd.scc
 include features/dmaengine/dmaengine.scc
diff --git a/meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc 
b/meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc
index 2a83303..6e4cc40 100644
--- a/meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc
+++ b/meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc
@@ -1,7 +1,7 @@
 kconf hardware emenlow.cfg

 kconf non-hardware reboot-quirk.cfg
-
+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc
 include features/drm-psb/drm-psb.scc
 include features/serial/8250.scc
diff --git a/meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc 
b/meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc
index 6e3d385..696ccf7 100644
--- a/meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc
+++ b/meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc
@@ -2,6 +2,7 @@ kconf hardware fishriver.cfg

 git merge yocto/emgd

+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc
 include features/drm-emgd/drm-emgd.scc
 include features/dmaengine/dmaengine.scc
diff --git a/meta/cfg/kernel-cache/bsp/fri2/fri2.scc 
b/meta/cfg/kernel-cache/bsp/fri2/fri2.scc
index 2d30049..ff38b2d 100644
--- a/meta/cfg/kernel-cache/bsp/fri2/fri2.scc
+++ b/meta/cfg/kernel-cache/bsp/fri2/fri2.scc
@@ -3,6 +3,7 @@ kconf hardware fri2.cfg
 git merge yocto/emgd

 include features/eg20t/eg20t.scc
+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc
 include features/drm-emgd/drm-emgd.scc
 include features/dmaengine/dmaengine.scc
diff --git a/meta/cfg/kernel-cache/bsp/romley/romley.scc 
b/meta/cfg/kernel-cache/bsp/romley/romley.scc
index 4152816..5d997e1 100644
--- a/meta/cfg/kernel-cache/bsp/romley/romley.scc
+++ b/meta/cfg/kernel-cache/bsp/romley/romley.scc
@@ -4,6 +4,7 @@ include features/i915/i915.scc
 include features/serial/8250.scc
 include features/uio/uio.scc
 include features/hugetlb/hugetlb.scc
+include features/intel-e1/intel-e100.scc
 include features/intel-e1/intel-e1.scc
 include features/ixgbe/ixgbe.scc

--
1.7.0.4



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] 答复: qemu boot fail(root-nfs: unknown option: mountprog=21111)

2011-09-08 Thread 蔡振军 
Hi Bruse,Scott
The information you supply is helpful to me. I have known what I need 
to make QEMU run.

Thanks (*^__^*)
Feye


-邮件原件-
发件人: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
发送时间: 2011年9月8日 15:38
收件人: 蔡振军
抄送: yocto@yoctoproject.org
主题: Re: [yocto] qemu boot fail(root-nfs: unknown option: mountprog=2)

On 11-09-08 01:49 AM, 蔡振军 wrote:
> Hi ALL
>
> QEMU run well with a pre-build kernel image from yocto site. Now just
> change the kernel to one built myself, some error information appeared
> about nfs. My kernel image version is 2.6.35 configured by
> versatile_defconfig. Error information as following:
>
> “root-nfs: unknown option: mountprog=2”,this message search nothing
> on google.
>
> Is there something wrong with .config? Add normally is there some
> special configuration I should do with kernel to fit QEMU

You can't change out the kernel version / tree and expect to use the full
functionality provided by the linux-yocto kernel. In this case there are
changes to NFS and rpc to support alternate rpc ports being used to support
usermode NFS. You would need to port and test the patches for this
which can be found on yocto/standard/base

Cheers,

Bruce

>
> Best regards
>
> Feye
>
> 蔡振军
>
> 网新技术有限公司物联网事业部
>
> 杭州天目山路226号网新大厦
>
> 电话-138 6745 1910
>
>
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto