Re: [OpenWrt-Devel] Howto debug init scripts like preinit?
Hi, I often use a simple bit-bang function at some high buad rate and one gpio pin. I hook a serial terminal to it. Depending on CPU speed, etc. interrupts may have to be disabled during the time the character is actually being sent. One character at 115,200 is 0.1ms so unless the CPU is very busy with time dependent stuff, most applications don't seem to mind that much. As an additional variation of this scheme, I make the pin bi-directional and hook my full software debugger to it. I can peek, poke and monitor memory in more or less real time. Works great. Saves LOTS of time. And makes things really clear. This feature would be a good add to OpenWRT in my copious spare time :)). regards, Wiz On Wed, 24 Mar 2010, Ferenc Wagner wrote: Daniel Dickinson csh...@csolve.net writes: You won't see anything from preinit with set -x because when preinit is first called there is no stdin/stdout. One of the things preinit does is attach itself to a terminal, if there is one (otherwise it just connects to a pseudo-terminal) Would putting /dev/console in the root filesystem solve this? Fakeroot could be used for that without requiring real root for image generation. -- Thanks, Feri. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Howto debug init scripts like preinit?
On Thu, Mar 25, 2010 at 5:18 AM, RHS Linux User x...@nei.mv.com wrote: Hi, I often use a simple bit-bang function at some high buad rate and one gpio pin. I hook a serial terminal to it. Depending on CPU speed, etc. interrupts may have to be disabled during the time the character is actually being sent. One character at 115,200 is 0.1ms so unless the CPU is very busy with time dependent stuff, most applications don't seem to mind that much. As an additional variation of this scheme, I make the pin bi-directional and hook my full software debugger to it. I can peek, poke and monitor memory in more or less real time. I use OpenOCD with a JTAG USB dongle and have gdb connect to the gdb server OpenOCD provides. This works great for things like the kernel, userspace programs etc. but I don't know how to go about using it to debug shell scripts. I've heard there is a bash debugger but I doubt that will help with ash built into BusyBox. Debugging shell scripts on a embedded target just isn't something I've ever needed to touch until now. Thanks for the ideas. Regards, Brian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
Right, 2.6.32 is preferred and will probably be supported for 2-3 years
[1]. However, targets proven to be stable at 2.6.30.10 won't be get
updated to 2.6.32.x for Backfire. Such updates will probably later in a
Backfire 10.03.1 point-release.
1. http://thread.gmane.org/gmane.linux.kernel/939800
--
-{Nico}
On 25/03/10 22:14, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
It seems 2.6.32.10 applies on all targets at 2.6.32.9, so I have no
problem switching to 2.6.32.10. Ideally, it would be great if all
targets at 2.6.32.x could be switched to the same version (coherency)
and such updates be committed before Friday evening.
--
-{Nico}
On 25/03/10 22:44, Matthias Buecher / Germany wrote:
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
If 2.6.32.10 will be *the* desired version, then Orion can be just
switched to it.
My WRT350Nv2 is really running fine with it.
File: target/linux/orion/Makefile
No need to rebase any patches.
Maddes
On 25.03.2010 22:57, Nico wrote:
It seems 2.6.32.10 applies on all targets at 2.6.32.9, so I have no
problem switching to 2.6.32.10. Ideally, it would be great if all
targets at 2.6.32.x could be switched to the same version (coherency)
and such updates be committed before Friday evening.
--
-{Nico}
On 25/03/10 22:44, Matthias Buecher / Germany wrote:
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 0/4] Add x86 kvm_guest subtarget
This patch series adds a new x86 subtarget for running inside a KVM guest.
Stijn Tintel (4):
kernel: move xen.mk to virtual.mk
kernel: add VirtIO device support
x86: add kvm_guest subtarget
kernel: virtio modules depend on x86_kvm_guest
package/kernel/modules/{xen.mk = virtual.mk} | 64 +++--
target/linux/x86/Makefile |2 +-
target/linux/x86/image/Config.in |7 +-
target/linux/x86/kvm_guest/base-files/etc/inittab |5 ++
target/linux/x86/kvm_guest/config-default | 10 +++
target/linux/x86/kvm_guest/config-default.bak | 29 +
target/linux/x86/kvm_guest/target.mk |2 +
7 files changed, 109 insertions(+), 10 deletions(-)
rename package/kernel/modules/{xen.mk = virtual.mk} (64%)
create mode 100644 target/linux/x86/kvm_guest/base-files/etc/inittab
create mode 100644 target/linux/x86/kvm_guest/config-default
create mode 100644 target/linux/x86/kvm_guest/config-default.bak
create mode 100644 target/linux/x86/kvm_guest/target.mk
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/4] x86: add kvm_guest subtarget
This patch adds a KVM guest subtarget to the x86 target. Since VirtIO is the preferred I/O virtualization platform for kvm, this target expects it's root device to be /dev/vda. Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- target/linux/x86/Makefile |2 +- target/linux/x86/image/Config.in |7 +++-- target/linux/x86/kvm_guest/base-files/etc/inittab |5 +++ target/linux/x86/kvm_guest/config-default | 10 +++ target/linux/x86/kvm_guest/config-default.bak | 29 + target/linux/x86/kvm_guest/target.mk |2 + 6 files changed, 51 insertions(+), 4 deletions(-) create mode 100644 target/linux/x86/kvm_guest/base-files/etc/inittab create mode 100644 target/linux/x86/kvm_guest/config-default create mode 100644 target/linux/x86/kvm_guest/config-default.bak create mode 100644 target/linux/x86/kvm_guest/target.mk diff --git a/target/linux/x86/Makefile b/target/linux/x86/Makefile index e9b7cba..71e95cc 100644 --- a/target/linux/x86/Makefile +++ b/target/linux/x86/Makefile @@ -10,7 +10,7 @@ ARCH:=i386 BOARD:=x86 BOARDNAME:=x86 FEATURES:=squashfs jffs2 ext2 vdi vmdk pcmcia tgz -SUBTARGETS=generic olpc xen_domu +SUBTARGETS=generic kvm_guest olpc xen_domu LINUX_VERSION:=2.6.32.9 diff --git a/target/linux/x86/image/Config.in b/target/linux/x86/image/Config.in index 9d17f37..88bf040 100644 --- a/target/linux/x86/image/Config.in +++ b/target/linux/x86/image/Config.in @@ -20,8 +20,8 @@ config X86_GRUB_SERIAL string prompt Serial port device depends X86_GRUB_IMAGES -default hvc0 if TARGET_x86_xen_domu -default ttyS0 if ! TARGET_x86_xen_domu +default hvc0 if (TARGET_x86_kvm_guest || TARGET_x86_xen_domu) +default ttyS0 if ! (TARGET_x86_kvm_guest || TARGET_x86_xen_domu) config X86_GRUB_BAUDRATE int Serial port baud rate @@ -37,8 +37,9 @@ config X86_GRUB_KERNELPART config X86_GRUB_ROOTPART string prompt Root partition on target device if X86_GRUB_IMAGES +default /dev/vda2 if TARGET_x86_kvm_guest default /dev/xvda2 if TARGET_x86_xen_domu -default /dev/sda2 if ! TARGET_x86_xen_domu +default /dev/sda2 if ! (TARGET_x86_kvm_guest || TARGET_x86_xen_domu) help The root partition on the final device. If you don't know, you probably want the default (/dev/sda2). diff --git a/target/linux/x86/kvm_guest/base-files/etc/inittab b/target/linux/x86/kvm_guest/base-files/etc/inittab new file mode 100644 index 000..469b8a9 --- /dev/null +++ b/target/linux/x86/kvm_guest/base-files/etc/inittab @@ -0,0 +1,5 @@ +::sysinit:/etc/init.d/rcS S boot +::shutdown:/etc/init.d/rcS K stop +tts/0::askfirst:/bin/ash --login +hvc0::askfirst:/bin/ash --login +tty1::askfirst:/bin/ash --login diff --git a/target/linux/x86/kvm_guest/config-default b/target/linux/x86/kvm_guest/config-default new file mode 100644 index 000..bd17667 --- /dev/null +++ b/target/linux/x86/kvm_guest/config-default @@ -0,0 +1,10 @@ +CONFIG_KVM=n +CONFIG_LGUEST=n +CONFIG_MICROCODE=n +CONFIG_NR_CPUS=4 +CONFIG_VIRTIO=y +CONFIG_VIRTIO_BLK=y +CONFIG_VIRTIO_PCI=y +CONFIG_VIRTIO_RING=y +CONFIG_VIRTUALIZATION=y +CONFIG_X86_PAT=n diff --git a/target/linux/x86/kvm_guest/config-default.bak b/target/linux/x86/kvm_guest/config-default.bak new file mode 100644 index 000..c0aa71a --- /dev/null +++ b/target/linux/x86/kvm_guest/config-default.bak @@ -0,0 +1,29 @@ +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_FREEZER=y +CONFIG_GENERIC_PENDING_IRQ=y +CONFIG_KVM=n +CONFIG_LGUEST=n +CONFIG_LOCK_KERNEL=y +CONFIG_MPENTIUM4=y +CONFIG_NR_CPUS=4 +CONFIG_PHYS_ADDR_T_64BIT=y +CONFIG_SCHED_MC=y +CONFIG_SCSI=n +CONFIG_SMP=y +CONFIG_STOP_MACHINE=y +CONFIG_VIRTIO=y +CONFIG_VIRTIO_BLK=y +CONFIG_VIRTIO_PCI=y +CONFIG_VIRTIO_RING=y +CONFIG_VIRTUALIZATION=y +CONFIG_X86_32_SMP=y +CONFIG_X86_CMOV=y +CONFIG_X86_CMPXCHG64=y +CONFIG_X86_DEBUGCTLMSR=y +CONFIG_X86_HT=y +CONFIG_X86_L1_CACHE_SHIFT=6 +CONFIG_X86_MINIMUM_CPU_FAMILY=5 +CONFIG_X86_PAE=n +CONFIG_X86_PAT=n +CONFIG_X86_TRAMPOLINE=y +CONFIG_X86_TSC=y diff --git a/target/linux/x86/kvm_guest/target.mk b/target/linux/x86/kvm_guest/target.mk new file mode 100644 index 000..611e3f0 --- /dev/null +++ b/target/linux/x86/kvm_guest/target.mk @@ -0,0 +1,2 @@ +BOARDNAME:=KVM Guest +DEFAULT_PACKAGES += kmod-virtio-balloon kmod-virtio-console kmod-virtio-net kmod-virtio-random -- 1.6.4.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/4] kernel: add VirtIO device support
Add support for VirtIO-based paravirtualized devices used by various virtualization platforms. Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- package/kernel/modules/virtual.mk | 52 + 1 files changed, 52 insertions(+), 0 deletions(-) diff --git a/package/kernel/modules/virtual.mk b/package/kernel/modules/virtual.mk index 39bf2b8..173b84a 100644 --- a/package/kernel/modules/virtual.mk +++ b/package/kernel/modules/virtual.mk @@ -7,6 +7,58 @@ VIRTUAL_MENU:=Virtualization Support + +define KernelPackage/virtio-balloon + SUBMENU:=$(VIRTUAL_MENU) + TITLE:=VirtIO balloon driver + DEPENDS:=...@target_x86 + KCONFIG:= \ + CONFIG_VIRTIO \ + CONFIG_VIRTIO_BALLOON + FILES:=$(LINUX_DIR)/drivers/virtio/virtio_balloon.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,06,virtio-balloon) +endef + +define KernelPackage/virtio-balloon/description + Kernel module for VirtIO memory ballooning support +endef + +$(eval $(call KernelPackage,virtio-balloon)) + + +define KernelPackage/virtio-net + SUBMENU:=$(VIRTUAL_MENU) + TITLE:=VirtIO network driver + DEPENDS:=...@target_x86 + KCONFIG:= \ + CONFIG_HVC_DRIVER=y \ + CONFIG_VIRTIO_NET + FILES:=$(LINUX_DIR)/drivers/net/virtio_net.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,50,virtio_net) +endef + +define KernelPackage/virtio-net/description + Kernel module for the VirtIO paravirtualized network device +endef + +$(eval $(call KernelPackage,virtio-net)) + + +define KernelPackage/virtio-random + SUBMENU:=$(VIRTUAL_MENU) + TITLE:=VirtIO Random Number Generator support + DEPENDS:=...@target_x86 + KCONFIG:=CONFIG_HW_RANDOM_VIRTIO + FILES:=$(LINUX_DIR)/drivers/char/hw_random/virtio-rng.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,09,virtio-rng) +endef + +define KernelPackage/virtio-random/description + Kernel module for the VirtIO Random Number Generator +endef + +$(eval $(call KernelPackage,virtio-random)) + define KernelPackage/xen-fs SUBMENU:=$(VIRTUAL_MENU) TITLE:=Xen filesystem -- 1.6.4.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/4] kernel: move xen.mk to virtual.mk
Move Xen kernel modules into a general virtualization category.
Signed-off-by: Stijn Tintel st...@linux-ipv6.be
---
package/kernel/modules/{xen.mk = virtual.mk} | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
rename package/kernel/modules/{xen.mk = virtual.mk} (94%)
diff --git a/package/kernel/modules/xen.mk b/package/kernel/modules/virtual.mk
similarity index 94%
rename from package/kernel/modules/xen.mk
rename to package/kernel/modules/virtual.mk
index 2252af4..39bf2b8 100644
--- a/package/kernel/modules/xen.mk
+++ b/package/kernel/modules/virtual.mk
@@ -5,10 +5,10 @@
# See /LICENSE for more information.
#
-XEN_MENU:=Xen paravirtualized guest support
+VIRTUAL_MENU:=Virtualization Support
define KernelPackage/xen-fs
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen filesystem
DEPENDS:=...@target_x86_xen_domu
KCONFIG:= \
@@ -26,7 +26,7 @@ $(eval $(call KernelPackage,xen-fs))
define KernelPackage/xen-evtchn
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen event channels
DEPENDS:=...@target_x86_xen_domu
KCONFIG:=CONFIG_XEN_DEV_EVTCHN
@@ -42,7 +42,7 @@ $(eval $(call KernelPackage,xen-evtchn))
# FIXME: the FB support should be moved to a separate kmod
define KernelPackage/xen-fbdev
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen virtual frame buffer
DEPENDS:=...@target_x86_xen_domu
KCONFIG:= \
@@ -79,7 +79,7 @@ $(eval $(call KernelPackage,xen-fbdev))
define KernelPackage/xen-kbddev
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen virtual keyboard and mouse
DEPENDS:=...@target_x86_xen_domu
KCONFIG:=CONFIG_XEN_KBDDEV_FRONTEND
@@ -95,7 +95,7 @@ $(eval $(call KernelPackage,xen-kbddev))
define KernelPackage/xen-netdev
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen network device frontend
DEPENDS:=...@target_x86_xen_domu
KCONFIG:=CONFIG_XEN_NETDEV_FRONTEND
--
1.6.4.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 4/4] kernel: virtio modules depend on x86_kvm_guest
Make the VirtIO modules depend on the new x86_kvm_guest subtarget. Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- package/kernel/modules/virtual.mk |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package/kernel/modules/virtual.mk b/package/kernel/modules/virtual.mk index 173b84a..9a9aa71 100644 --- a/package/kernel/modules/virtual.mk +++ b/package/kernel/modules/virtual.mk @@ -11,7 +11,7 @@ VIRTUAL_MENU:=Virtualization Support define KernelPackage/virtio-balloon SUBMENU:=$(VIRTUAL_MENU) TITLE:=VirtIO balloon driver - DEPENDS:=...@target_x86 + DEPENDS:=...@target_x86_kvm_guest KCONFIG:= \ CONFIG_VIRTIO \ CONFIG_VIRTIO_BALLOON @@ -29,7 +29,7 @@ $(eval $(call KernelPackage,virtio-balloon)) define KernelPackage/virtio-net SUBMENU:=$(VIRTUAL_MENU) TITLE:=VirtIO network driver - DEPENDS:=...@target_x86 + DEPENDS:=...@target_x86_kvm_guest KCONFIG:= \ CONFIG_HVC_DRIVER=y \ CONFIG_VIRTIO_NET @@ -47,7 +47,7 @@ $(eval $(call KernelPackage,virtio-net)) define KernelPackage/virtio-random SUBMENU:=$(VIRTUAL_MENU) TITLE:=VirtIO Random Number Generator support - DEPENDS:=...@target_x86 + DEPENDS:=...@target_x86_kvm_guest KCONFIG:=CONFIG_HW_RANDOM_VIRTIO FILES:=$(LINUX_DIR)/drivers/char/hw_random/virtio-rng.$(LINUX_KMOD_SUFFIX) AUTOLOAD:=$(call AutoLoad,09,virtio-rng) -- 1.6.4.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
On Thu, Mar 25, 2010 at 11:59:56PM +0100, Matthias Buecher / Germany wrote:
If 2.6.32.10 will be *the* desired version, then Orion can be just
switched to it.
My WRT350Nv2 is really running fine with it.
File: target/linux/orion/Makefile
No need to rebase any patches.
Same for target/linux/ar71xx/Makefile on WRT160NL working fine since
last week.
-
Otto
Maddes
On 25.03.2010 22:57, Nico wrote:
It seems 2.6.32.10 applies on all targets at 2.6.32.9, so I have no
problem switching to 2.6.32.10. Ideally, it would be great if all
targets at 2.6.32.x could be switched to the same version (coherency)
and such updates be committed before Friday evening.
--
-{Nico}
On 25/03/10 22:44, Matthias Buecher / Germany wrote:
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of
the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
Seems a bit like overkill to me, but I guess that's not my call to make. Thanks for your patch and your tests. Bernhard 2010/3/24 Otto Solares so...@guug.org: On Wed, Mar 24, 2010 at 02:39:51PM +0100, Bernhard Loos wrote: After a suggestion from xMff, I dedicded to use a uci-defaults script, as this should fit the needs. Use it instead of the firstboot script in the original patch. I can't test it, as I don't have the device with me right now, but it's trivial. Based on others ar71xx uci-defaults scripts and yours I think the attached patch is a little better. Tested successfully with your original patch in both pure jffs2 and squashfs and it works fine. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 0/4] Add x86 kvm_guest subtarget
This patch series adds a new x86 subtarget for running inside a KVM guest.
The v2 series fixes some copy-paste errors and an accidentally commited file.
Stijn Tintel (4):
kernel: move xen.mk to virtual.mk
kernel: add VirtIO device support
x86: add kvm_guest subtarget
kernel: virtio modules depend on x86_kvm_guest
package/kernel/modules/{xen.mk = virtual.mk} | 60 ++--
target/linux/x86/Makefile |2 +-
target/linux/x86/image/Config.in |7 ++-
target/linux/x86/kvm_guest/base-files/etc/inittab |5 ++
target/linux/x86/kvm_guest/config-default | 10
target/linux/x86/kvm_guest/target.mk |2 +
6 files changed, 76 insertions(+), 10 deletions(-)
rename package/kernel/modules/{xen.mk = virtual.mk} (64%)
create mode 100644 target/linux/x86/kvm_guest/base-files/etc/inittab
create mode 100644 target/linux/x86/kvm_guest/config-default
create mode 100644 target/linux/x86/kvm_guest/target.mk
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 3/4] x86: add kvm_guest subtarget
Add a KVM guest subtarget to the x86 target. Since VirtIO is the preferred I/O virtualization platform for kvm, this target expects it's root device to be /dev/vda. Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- target/linux/x86/Makefile |2 +- target/linux/x86/image/Config.in |7 --- target/linux/x86/kvm_guest/base-files/etc/inittab |5 + target/linux/x86/kvm_guest/config-default | 10 ++ target/linux/x86/kvm_guest/target.mk |2 ++ 5 files changed, 22 insertions(+), 4 deletions(-) create mode 100644 target/linux/x86/kvm_guest/base-files/etc/inittab create mode 100644 target/linux/x86/kvm_guest/config-default create mode 100644 target/linux/x86/kvm_guest/target.mk diff --git a/target/linux/x86/Makefile b/target/linux/x86/Makefile index e9b7cba..71e95cc 100644 --- a/target/linux/x86/Makefile +++ b/target/linux/x86/Makefile @@ -10,7 +10,7 @@ ARCH:=i386 BOARD:=x86 BOARDNAME:=x86 FEATURES:=squashfs jffs2 ext2 vdi vmdk pcmcia tgz -SUBTARGETS=generic olpc xen_domu +SUBTARGETS=generic kvm_guest olpc xen_domu LINUX_VERSION:=2.6.32.9 diff --git a/target/linux/x86/image/Config.in b/target/linux/x86/image/Config.in index 9d17f37..88bf040 100644 --- a/target/linux/x86/image/Config.in +++ b/target/linux/x86/image/Config.in @@ -20,8 +20,8 @@ config X86_GRUB_SERIAL string prompt Serial port device depends X86_GRUB_IMAGES -default hvc0 if TARGET_x86_xen_domu -default ttyS0 if ! TARGET_x86_xen_domu +default hvc0 if (TARGET_x86_kvm_guest || TARGET_x86_xen_domu) +default ttyS0 if ! (TARGET_x86_kvm_guest || TARGET_x86_xen_domu) config X86_GRUB_BAUDRATE int Serial port baud rate @@ -37,8 +37,9 @@ config X86_GRUB_KERNELPART config X86_GRUB_ROOTPART string prompt Root partition on target device if X86_GRUB_IMAGES +default /dev/vda2 if TARGET_x86_kvm_guest default /dev/xvda2 if TARGET_x86_xen_domu -default /dev/sda2 if ! TARGET_x86_xen_domu +default /dev/sda2 if ! (TARGET_x86_kvm_guest || TARGET_x86_xen_domu) help The root partition on the final device. If you don't know, you probably want the default (/dev/sda2). diff --git a/target/linux/x86/kvm_guest/base-files/etc/inittab b/target/linux/x86/kvm_guest/base-files/etc/inittab new file mode 100644 index 000..469b8a9 --- /dev/null +++ b/target/linux/x86/kvm_guest/base-files/etc/inittab @@ -0,0 +1,5 @@ +::sysinit:/etc/init.d/rcS S boot +::shutdown:/etc/init.d/rcS K stop +tts/0::askfirst:/bin/ash --login +hvc0::askfirst:/bin/ash --login +tty1::askfirst:/bin/ash --login diff --git a/target/linux/x86/kvm_guest/config-default b/target/linux/x86/kvm_guest/config-default new file mode 100644 index 000..2231d2e --- /dev/null +++ b/target/linux/x86/kvm_guest/config-default @@ -0,0 +1,10 @@ +CONFIG_HAVE_KVM=n +CONFIG_MICROCODE=n +CONFIG_NR_CPUS=4 +CONFIG_VIRTIO=y +CONFIG_VIRTIO_BLK=y +CONFIG_VIRTIO_CONSOLE=y +CONFIG_VIRTIO_PCI=y +CONFIG_VIRTIO_RING=y +CONFIG_VIRTUALIZATION=y +CONFIG_X86_PAT=n diff --git a/target/linux/x86/kvm_guest/target.mk b/target/linux/x86/kvm_guest/target.mk new file mode 100644 index 000..7e48f64 --- /dev/null +++ b/target/linux/x86/kvm_guest/target.mk @@ -0,0 +1,2 @@ +BOARDNAME:=KVM Guest +DEFAULT_PACKAGES += kmod-virtio-balloon kmod-virtio-net kmod-virtio-random -- 1.6.4.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 2/4] kernel: add VirtIO device support
Add support for VirtIO-based paravirtualized devices used by various virtualization platforms. Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- package/kernel/modules/virtual.mk | 48 + 1 files changed, 48 insertions(+), 0 deletions(-) diff --git a/package/kernel/modules/virtual.mk b/package/kernel/modules/virtual.mk index 39bf2b8..4aa1d8c 100644 --- a/package/kernel/modules/virtual.mk +++ b/package/kernel/modules/virtual.mk @@ -7,6 +7,54 @@ VIRTUAL_MENU:=Virtualization Support + +define KernelPackage/virtio-balloon + SUBMENU:=$(VIRTUAL_MENU) + TITLE:=VirtIO balloon driver + DEPENDS:=...@target_x86 + KCONFIG:=CONFIG_VIRTIO_BALLOON + FILES:=$(LINUX_DIR)/drivers/virtio/virtio_balloon.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,06,virtio-balloon) +endef + +define KernelPackage/virtio-balloon/description + Kernel module for VirtIO memory ballooning support +endef + +$(eval $(call KernelPackage,virtio-balloon)) + + +define KernelPackage/virtio-net + SUBMENU:=$(VIRTUAL_MENU) + TITLE:=VirtIO network driver + DEPENDS:=...@target_x86 + KCONFIG:=CONFIG_VIRTIO_NET + FILES:=$(LINUX_DIR)/drivers/net/virtio_net.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,50,virtio_net) +endef + +define KernelPackage/virtio-net/description + Kernel module for the VirtIO paravirtualized network device +endef + +$(eval $(call KernelPackage,virtio-net)) + + +define KernelPackage/virtio-random + SUBMENU:=$(VIRTUAL_MENU) + TITLE:=VirtIO Random Number Generator support + DEPENDS:=...@target_x86 + KCONFIG:=CONFIG_HW_RANDOM_VIRTIO + FILES:=$(LINUX_DIR)/drivers/char/hw_random/virtio-rng.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,09,virtio-rng) +endef + +define KernelPackage/virtio-random/description + Kernel module for the VirtIO Random Number Generator +endef + +$(eval $(call KernelPackage,virtio-random)) + define KernelPackage/xen-fs SUBMENU:=$(VIRTUAL_MENU) TITLE:=Xen filesystem -- 1.6.4.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 1/4] kernel: move xen.mk to virtual.mk
Move Xen kernel modules into a general virtualization category.
Signed-off-by: Stijn Tintel st...@linux-ipv6.be
---
package/kernel/modules/{xen.mk = virtual.mk} | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
rename package/kernel/modules/{xen.mk = virtual.mk} (94%)
diff --git a/package/kernel/modules/xen.mk b/package/kernel/modules/virtual.mk
similarity index 94%
rename from package/kernel/modules/xen.mk
rename to package/kernel/modules/virtual.mk
index 2252af4..39bf2b8 100644
--- a/package/kernel/modules/xen.mk
+++ b/package/kernel/modules/virtual.mk
@@ -5,10 +5,10 @@
# See /LICENSE for more information.
#
-XEN_MENU:=Xen paravirtualized guest support
+VIRTUAL_MENU:=Virtualization Support
define KernelPackage/xen-fs
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen filesystem
DEPENDS:=...@target_x86_xen_domu
KCONFIG:= \
@@ -26,7 +26,7 @@ $(eval $(call KernelPackage,xen-fs))
define KernelPackage/xen-evtchn
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen event channels
DEPENDS:=...@target_x86_xen_domu
KCONFIG:=CONFIG_XEN_DEV_EVTCHN
@@ -42,7 +42,7 @@ $(eval $(call KernelPackage,xen-evtchn))
# FIXME: the FB support should be moved to a separate kmod
define KernelPackage/xen-fbdev
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen virtual frame buffer
DEPENDS:=...@target_x86_xen_domu
KCONFIG:= \
@@ -79,7 +79,7 @@ $(eval $(call KernelPackage,xen-fbdev))
define KernelPackage/xen-kbddev
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen virtual keyboard and mouse
DEPENDS:=...@target_x86_xen_domu
KCONFIG:=CONFIG_XEN_KBDDEV_FRONTEND
@@ -95,7 +95,7 @@ $(eval $(call KernelPackage,xen-kbddev))
define KernelPackage/xen-netdev
- SUBMENU:=$(XEN_MENU)
+ SUBMENU:=$(VIRTUAL_MENU)
TITLE:=Xen network device frontend
DEPENDS:=...@target_x86_xen_domu
KCONFIG:=CONFIG_XEN_NETDEV_FRONTEND
--
1.6.4.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 4/4] kernel: virtio modules depend on x86_kvm_guest
Make the VirtIO modules depend on the new x86_kvm_guest subtarget. Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- package/kernel/modules/virtual.mk |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package/kernel/modules/virtual.mk b/package/kernel/modules/virtual.mk index 4aa1d8c..2f870a2 100644 --- a/package/kernel/modules/virtual.mk +++ b/package/kernel/modules/virtual.mk @@ -11,7 +11,7 @@ VIRTUAL_MENU:=Virtualization Support define KernelPackage/virtio-balloon SUBMENU:=$(VIRTUAL_MENU) TITLE:=VirtIO balloon driver - DEPENDS:=...@target_x86 + DEPENDS:=...@target_x86_kvm_guest KCONFIG:=CONFIG_VIRTIO_BALLOON FILES:=$(LINUX_DIR)/drivers/virtio/virtio_balloon.$(LINUX_KMOD_SUFFIX) AUTOLOAD:=$(call AutoLoad,06,virtio-balloon) @@ -27,7 +27,7 @@ $(eval $(call KernelPackage,virtio-balloon)) define KernelPackage/virtio-net SUBMENU:=$(VIRTUAL_MENU) TITLE:=VirtIO network driver - DEPENDS:=...@target_x86 + DEPENDS:=...@target_x86_kvm_guest KCONFIG:=CONFIG_VIRTIO_NET FILES:=$(LINUX_DIR)/drivers/net/virtio_net.$(LINUX_KMOD_SUFFIX) AUTOLOAD:=$(call AutoLoad,50,virtio_net) @@ -43,7 +43,7 @@ $(eval $(call KernelPackage,virtio-net)) define KernelPackage/virtio-random SUBMENU:=$(VIRTUAL_MENU) TITLE:=VirtIO Random Number Generator support - DEPENDS:=...@target_x86 + DEPENDS:=...@target_x86_kvm_guest KCONFIG:=CONFIG_HW_RANDOM_VIRTIO FILES:=$(LINUX_DIR)/drivers/char/hw_random/virtio-rng.$(LINUX_KMOD_SUFFIX) AUTOLOAD:=$(call AutoLoad,09,virtio-rng) -- 1.6.4.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [patch] ag71xx: Add netpoll support
This patch adds support for polling interrupts, used by
netconsole and the likes.
Tested on d-link dir-615 C1 using netconsole.
Signed-off-by: Pat Erley pat-l...@erley.org
---
I suspect that I'm not doing the {enable,disable}_irq
corretly, but 'it works for me'.
---
--- target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx_main.c (revision 20434)
+++ target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx_main.c (working copy)
@@ -926,6 +926,20 @@
/* TODO */
}
+#ifdef CONFIG_NET_POLL_CONTROLLER
+/*
+ * Polling 'interrupt' - used by things like netconsole to send skbs
+ * without having to re-enable interrupts. It's not called while
+ * the interrupt routine is executing.
+ */
+static void ag71xx_netpoll(struct net_device *dev)
+{
+ disable_irq(dev-irq);
+ ag71xx_interrupt(dev-irq, dev);
+ enable_irq(dev-irq);
+}
+#endif
+
static const struct net_device_ops ag71xx_netdev_ops = {
.ndo_open = ag71xx_open,
.ndo_stop = ag71xx_stop,
@@ -936,6 +950,9 @@
.ndo_change_mtu = eth_change_mtu,
.ndo_set_mac_address= eth_mac_addr,
.ndo_validate_addr = eth_validate_addr,
+#ifdef CONFIG_NET_POLL_CONTROLLER
+.ndo_poll_controller= ag71xx_netpoll,
+#endif
};
static int __init ag71xx_probe(struct platform_device *pdev)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] FreeSWITCH 1.0.5-latest OpenWRT package repository
A note to anyone interested in FreeSWITCH. If you want to try out, or help me debug, FreeSWITCH 1.0.5 (not yet released), I have a git repo that I periodically update the the latest available build of 1.0.5 (from http://latest.freeswitch.org). My repository it a Git repository for all my personal feeds for OpenWRT (currently only freeswitch-latest) http://cshore.is-a-geek.com/openwrt-repo/feed You can add to your feeds by adding the following line to your feeds.conf src-git cshore_feed http://cshore.is-a-geek.com/openwrt-repo/feed and scripts/feed update -a scripts/feed install -a, as usual. Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
