You just need to enable ethernet bridging and tun network on the host kernel, setup a bridge adapter on your host system, and then use the right command line settings to qemu as per the standard Linux guest. -Christoffer On Mon, May 13, 2013 at 9:16 AM, Howard Mao <zhehao.mao@xxxxxxxxx> wrote: > How exactly did you get bridged networking work in the guest? > > > On Mon, May 13, 2013 at 11:49 AM, Howard Mao <zhehao.mao@xxxxxxxxx> wrote: >> >> OK, I've figured it out. For some reason, the ethernet device won't be >> recognized unless you call "usb start" in u-boot. >> >> >> On Mon, May 13, 2013 at 2:04 AM, Christoffer Dall <cdall@xxxxxxxxxxxxxxx> >> wrote: >>> >>> I don't remember exactly how the boot logs appear, but ohci is usb >>> 1.1, and I believe the USB adapter is on the usb2 subsystem, so you >>> sohuld see seme EHCI messages too, but the log also says usb2, so >>> maybe you're fine. In any case, getting the adapter to show up in >>> /sys/.... is a matter of enabling the right driver and having the >>> right DT afaik, so that's where to start. >>> >>> -Christoffer >>> >>> On Sun, May 12, 2013 at 3:03 PM, Howard Mao <zhehao.mao@xxxxxxxxx> wrote: >>> > Well, the boot log has messages like >>> > >>> > usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 >>> > usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >>> > usb usb2: Product: EXYNOS OHCI Host Controller >>> > usb usb2: Manufacturer: Linux 3.9.0-rc2-12896-g58e4663 ohci_hcd >>> > usb usb2: SerialNumber: 12120000.usb >>> > >>> > And I looked in /sys/bus/usb/devices/ and found four directories. Two >>> > of >>> > them had devices attached to them, which were >>> > >>> > S5P EHCI Host Controller >>> > EXYNOS OHCI Host Controller >>> > >>> > So the USB subsystem is working. I'll try comparing my current >>> > configuration >>> > with the one I used earlier and see whether certain drivers were >>> > disabled. >>> > >>> > >>> > On Sun, May 12, 2013 at 3:02 PM, Christoffer Dall >>> > <cdall@xxxxxxxxxxxxxxx> >>> > wrote: >>> >> >>> >> Did you check that your USB subsystem is up? >>> >> >>> >> The ethernet adapter is wired (for whatever reason) over the USB bus >>> >> on >>> >> the Arndale board, so USB is a prerequisite for networking. >>> >> >>> >> You should check the Android kernel boot output and compare it to the >>> >> kernel where you have working networking. >>> >> >>> >> -Christoffer >>> >> >>> >> On Sun, May 12, 2013 at 10:34:04AM -0400, Howard Mao wrote: >>> >> > The device does not appear in /sys/class/net. I just checked my >>> >> > kernel >>> >> > configuration, the "AX88xxx based USB 2.0 Ethernet Adapters" driver >>> >> > is >>> >> > selected. >>> >> > >>> >> > >>> >> > On Sun, May 12, 2013 at 1:26 AM, Christoffer Dall >>> >> > <cdall@xxxxxxxxxxxxxxx>wrote: >>> >> > >>> >> > > so you need to verify that the device is there under >>> >> > > /sys/class/net >>> >> > > and then play with the netconfig tool in android to see if you can >>> >> > > bring up the device. >>> >> > > >>> >> > > On Sat, May 11, 2013 at 5:56 PM, Howard Mao <zhehao.mao@xxxxxxxxx> >>> >> > > wrote: >>> >> > > > OK, I've figured out the ethernet controller model. It's >>> >> > > > AX88760, >>> >> > > > which >>> >> > > is >>> >> > > > an asix chip. Which is weird because I have the asix driver >>> >> > > > enabled. >>> >> > > > It >>> >> > > even >>> >> > > > prints a message about it in the boot log. >>> >> > > > >>> >> > > > usbcore: registered new interface driver asix >>> >> > > > >>> >> > > > >>> >> > > > On Sat, May 11, 2013 at 8:52 PM, Howard Mao >>> >> > > > <zhehao.mao@xxxxxxxxx> >>> >> > > wrote: >>> >> > > >> >>> >> > > >> I'm not sure, what ethernet controller does the Arndale board >>> >> > > >> use? >>> >> > > >> I'm >>> >> > > >> having trouble finding it. >>> >> > > >> >>> >> > > >> If I look in /sys/class/net, all I see is lo, the loopback >>> >> > > >> interface. >>> >> > > >> >>> >> > > >> Also, I've found this bug report >>> >> > > >> https://bugs.launchpad.net/arndale/+bug/1081383 for Ubuntu on >>> >> > > >> Arndale. >>> >> > > They >>> >> > > >> must have resolved it though because Ethernet was working when >>> >> > > >> I >>> >> > > >> was >>> >> > > using >>> >> > > >> Ubuntu. >>> >> > > >> >>> >> > > >> >>> >> > > >> On Fri, May 10, 2013 at 6:43 PM, Christoffer Dall < >>> >> > > cdall@xxxxxxxxxxxxxxx> >>> >> > > >> wrote: >>> >> > > >>> >>> >> > > >>> On Tue, May 07, 2013 at 11:15:34AM -0400, Howard Mao wrote: >>> >> > > >>> > I'm trying to get networking working on the host now, but >>> >> > > >>> > there >>> >> > > doesn't >>> >> > > >>> > seem to be an eth0 interface at all (or anything other than >>> >> > > >>> > a >>> >> > > loopback >>> >> > > >>> > interface). I've searched online, but I couldn't find >>> >> > > >>> > anything >>> >> > > >>> > about >>> >> > > >>> > this. >>> >> > > >>> > Has anyone seen this problem before? >>> >> > > >>> > >>> >> > > >>> Did you make sure to enable the config for the right adapter >>> >> > > >>> in >>> >> > > >>> the >>> >> > > >>> kernel? >>> >> > > >>> >>> >> > > >>> What does the sysfs files tell you? Does is pick up a network >>> >> > > >>> device? >>> >> > > >>> >>> >> > > >>> -Christoffer >>> >> > > >> >>> >> > > >> >>> >> > > > >>> >> > > >>> > >>> > >> >> > _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
