iw dev wlan0 interface add [virtual-sta-name] type station
iw dev wlan0 interface add [virtual-ap-name] type __ap
ip link set [interface-name] address [unique-mac-addr]
iw dev [dev-name] del
$ cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
wlan0: 0000 56. -54. -256 0 0 0 0 0 0
OR
$ iw dev wlan0 link
Connected to 00:10:7A:93:AE:BF (on wlan0)
SSID: SECRETSSID
freq: 2462
RX: 89045514 bytes (194863 packets)
TX: 34783321 bytes (164504 packets)
signal: -54 dBm
tx bitrate: 48.0 MBit/s
when I cross-compile OpenJDK 9 for ARM32 I pass the following configure options configure # these options tell openjdk to do a cross compile build. --build=x86_64-unknown-linux-gnu --host=arm-buildroot-linux-gnueabi --target=arm-buildroot-linux-gnueabi # these two options enable zero --with-jvm-interpreter=cpp --with-jvm-variants=zero # specific options to make the build find the X and freetype headers and librarys found on the ARM32 root filesystem. --disable-freetype-bundling --with-freetype-include=/home/xranby/rpi-buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/include/freetype2 --with-freetype-lib=/home/xranby/rpi-buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib --with-freetype=/home/xranby/rpi-buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/ --with-x=/home/xranby/rpi-buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/include # the sysroot shall point to the ARM32 root file system, the build will use librarys inside the sys root during linking native libraries. --with-sys-root=/home/xranby/rpi-buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot # The tools dir contains binarys to run on the host x86 system, you may point this to your system root dir / # in my case the tools i use have been compiled by buildroot thus I use the buildroot tools dir. --with-tools-dir=/home/xranby/rpi-buildroot/output/host # OpenJDK 9 require OpenJDK 8, i point with boot jdk to an OpenJDK 8 image that can be run on the host x86 system. --with-boot-jdk=/home/xranby/images-jdk8/j2sdk-image/ # some parts of the openjdk build still expect that the cross compile tools are found in the system PATH # on my system i have to explicitly tell where the tools are located because my cross compile toolchain is not found on the path. # i use gcc to do the linking instead of ld because the openjdk build passes -Xlinker -z OBJCOPY=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-objcopy STRIP=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-strip CPP=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-cpp CXX=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-g++ CC=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-gcc LD=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-gcc CPP_FLAGS=-lstdc++ CXX_FLAGS=-lstdc++ when running make i pass the following options to make # BUILD_CC and BUILD_LD shall point to host x86 executables. BUILD_CC=gcc BUILD_LD=gcc OBJCOPY=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-objcopy STRIP=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-strip CPP=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-cpp CXX=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-g++ CC=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-gcc LD=/home/xranby/rpi-buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-gcc #and finally the target, this will build compact profiles, jre and jdk images. all images profiles CONF=linux-arm-normal-zero-release I have automated these configure and make options for openjdk 9 into buildroot build scripts https://github.com/xranby/rpi-buildroot/tree/openjdk > > I've done Zero builds before but have never used OpenJDK's cross-compile > feature to build it on ARMv7. There is an Arm32 bit JIT in IcedTea[1], > but I don't know if that can be cross-compiled. If you cross compile icedtea then you need to make sure that the bytecode generator tool is compiled by the host x86 toolchain. openembedded meta-java contains buildscripts that can cross compile the Arm32 JIT found in IcedTea. https://github.com/woglinde/meta-java Cheers Xerxes
~/.vimrc should help:set tags=./tags,tags;$HOME
tags file in the directory of the current file, in the current directory and up and up until your $HOME (that's the meaning of the semicolon), stopping on the first hit.
| PID Type | PID Name | PID<3:0>* |
| Token | OUT | 0001b |
| IN | 1001b | |
| SOF | 0101b | |
| SETUP | 1101b | |
| Data | DATA0 | 0011b |
| DATA1 | 1011b | |
| DATA2 | 0111b | |
| MDATA | 1111b | |
| Handshake | ACK | 0010b |
| NAK | 1010b | |
| STALL | 1110b | |
| NYET | 0110b | |
| Special | PRE | 1100b |
| ERR | 1100b | |
| SPLIT | 1000b | |
| PING | 0100b | |
| Reserved | 0000b |
/etc/ssh/ssh_config for Linux and ~/.ssh/config for Mac:
Host *
ServerAliveInterval 120
dmesg to get the
kernel output for the event. It will look something like this:input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:04.1/usb2/2-4/2-4.2/2-4.2:1.0/input/input16
$ sudo bash -c "echo -n 2-4.2:1.0 >/sys/bus/usb/drivers/usbhid/unbind"
lsusb again for the device and you should see the report descriptor
in the output!$ lsusb -vd 054c:0268
Source:
http://www.slashdev.ca/2010/05/08/get-usb-report-descriptor-with-linux/