search for: fastboot

Has anyone used fastboot together with the Google Pixel 3a/3a XL phone? I cannot get it to be recognized and wonder if the version of fastboot available for Centos 7 may not be recent enough? It does work with older phones I have so the setup should be correct.

...d to use newer than stock/epel packages in the past for various phones. Just get the latest binaries from here: https://dl.google.com/android/repository/platform-tools-latest-linux.zip hth --- Sent from the Delta quadrant using Borg technology! On 2019-07-26 03:28, H wrote: > Has anyone used fastboot together with the Google Pixel 3a/3a XL > phone? I cannot get it to be recognized and wonder if the version of > fastboot available for Centos 7 may not be recent enough? It does work > with older phones I have so the setup should be correct. > > ____________________________________...

...It works fine for virtio-pci (where "dma-coherent" >> is used) and it also works on the fastmodel if you disable cache-modelling >> (which is needed to make the thing run at a usable pace) so we didn't spot >> this in testing. >> >>> Could we identify fastboot and do the special dance just for it? >> >> [assuming you mean fastmodel instead of fastboot] >> >>> I'd like to do that instead. It's fastboot doing the unreasonable thing >>> here and deviating from what every other legacy device without exception >&...

...It works fine for virtio-pci (where "dma-coherent" >> is used) and it also works on the fastmodel if you disable cache-modelling >> (which is needed to make the thing run at a usable pace) so we didn't spot >> this in testing. >> >>> Could we identify fastboot and do the special dance just for it? >> >> [assuming you mean fastmodel instead of fastboot] >> >>> I'd like to do that instead. It's fastboot doing the unreasonable thing >>> here and deviating from what every other legacy device without exception >&...

...ctly what I feared. Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" is used) and it also works on the fastmodel if you disable cache-modelling (which is needed to make the thing run at a usable pace) so we didn't spot this in testing. > Could we identify fastboot and do the special dance just for it? [assuming you mean fastmodel instead of fastboot] > I'd like to do that instead. It's fastboot doing the unreasonable thing > here and deviating from what every other legacy device without exception > did for years. If this means fastboot wil...

...ctly what I feared. Yes, sorry about this. It works fine for virtio-pci (where "dma-coherent" is used) and it also works on the fastmodel if you disable cache-modelling (which is needed to make the thing run at a usable pace) so we didn't spot this in testing. > Could we identify fastboot and do the special dance just for it? [assuming you mean fastmodel instead of fastboot] > I'd like to do that instead. It's fastboot doing the unreasonable thing > here and deviating from what every other legacy device without exception > did for years. If this means fastboot wil...

On Wed, Feb 01, 2017 at 09:19:22PM +0200, Michael S. Tsirkin wrote: > On Wed, Feb 01, 2017 at 06:27:09PM +0000, Will Deacon wrote: > > On Wed, Feb 01, 2017 at 08:09:21PM +0200, Michael S. Tsirkin wrote: > > > I'd like to do that instead. It's fastboot doing the unreasonable thing > > > here and deviating from what every other legacy device without exception > > > did for years. If this means fastboot will need to update to virtio 1, > > > all the better. > > > > The problem still exists with virtio 1, unle...

On Wed, Feb 01, 2017 at 09:19:22PM +0200, Michael S. Tsirkin wrote: > On Wed, Feb 01, 2017 at 06:27:09PM +0000, Will Deacon wrote: > > On Wed, Feb 01, 2017 at 08:09:21PM +0200, Michael S. Tsirkin wrote: > > > I'd like to do that instead. It's fastboot doing the unreasonable thing > > > here and deviating from what every other legacy device without exception > > > did for years. If this means fastboot will need to update to virtio 1, > > > all the better. > > > > The problem still exists with virtio 1, unle...

...here "dma-coherent" > > > is used) and it also works on the fastmodel if you disable cache-modelling > > > (which is needed to make the thing run at a usable pace) so we didn't spot > > > this in testing. > > > > > > > Could we identify fastboot and do the special dance just for it? > > > > > > [assuming you mean fastmodel instead of fastboot] > > > > > > > I'd like to do that instead. It's fastboot doing the unreasonable thing > > > > here and deviating from what every other leg...

...000-0xd50cffff irq 34 at device 0.0 on pci2 bge0: APE FW version: NCSI v1.0.80.0 bge0: attempting to allocate 1 MSI vectors (8 supported) msi: routing MSI IRQ 264 to local APIC 0 vector 59 bge0: using IRQ 264 for MSI bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E bge0: Disabling fastboot bge0: Disabling fastboot miibus0: <MII bus> on bge0 brgphy0: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus0 brgphy0: OUI 0x001be9, model 0x0036, rev. 0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, aut...

...; > On Wed, Feb 01, 2017 at 09:19:22PM +0200, Michael S. Tsirkin wrote: > >> On Wed, Feb 01, 2017 at 06:27:09PM +0000, Will Deacon wrote: > >>> On Wed, Feb 01, 2017 at 08:09:21PM +0200, Michael S. Tsirkin wrote: > >>>> I'd like to do that instead. It's fastboot doing the unreasonable thing > >>>> here and deviating from what every other legacy device without exception > >>>> did for years. If this means fastboot will need to update to virtio 1, > >>>> all the better. > >>> > >>> The prob...

...; > On Wed, Feb 01, 2017 at 09:19:22PM +0200, Michael S. Tsirkin wrote: > >> On Wed, Feb 01, 2017 at 06:27:09PM +0000, Will Deacon wrote: > >>> On Wed, Feb 01, 2017 at 08:09:21PM +0200, Michael S. Tsirkin wrote: > >>>> I'd like to do that instead. It's fastboot doing the unreasonable thing > >>>> here and deviating from what every other legacy device without exception > >>>> did for years. If this means fastboot will need to update to virtio 1, > >>>> all the better. > >>> > >>> The prob...

...sorry about this. It works fine for virtio-pci (where "dma-coherent" > is used) and it also works on the fastmodel if you disable cache-modelling > (which is needed to make the thing run at a usable pace) so we didn't spot > this in testing. > > > Could we identify fastboot and do the special dance just for it? > > [assuming you mean fastmodel instead of fastboot] > > > I'd like to do that instead. It's fastboot doing the unreasonable thing > > here and deviating from what every other legacy device without exception > > did for yea...

...NFIG_ARM64)) > + if ((IS_ENABLED(CONFIG_ARM) || IS_ENABLED(CONFIG_ARM64)) && > + device_get_dma_attr(&vdev->dev) == DEV_DMA_COHERENT) > return !virtio_has_feature(vdev, VIRTIO_F_VERSION_1); > > return false; This is exactly what I feared. Could we identify fastboot and do the special dance just for it? I'd like to do that instead. It's fastboot doing the unreasonable thing here and deviating from what every other legacy device without exception did for years. If this means fastboot will need to update to virtio 1, all the better. > -- > 2.11....

...hed the reboot. Last weekend we rebooted the same box and faced the same issue, however, we sent the break, commented out (last "0" in /etc/fstab did not work neither) all OCFS2 lines in /etc/fstab and it booted fine. Then we mount -a them and life was good. Also we added later on the fastboot to the grub.conf, then booted it - no problem for obvious reasons. If anyone experienced the same issue - would you mind to light into the tonnel and share your experience and perhaps the fix? Thanks Sergey Prilutsky -------------- next part -------------- An HTML attachment...

By forcing on DMA API usage for ARM systems, we have inadvertently kicked open a hornets' nest in terms of cache-coherency. Namely that unless the virtio device is explicitly described as capable of coherent DMA by firmware, the DMA APIs on ARM and other DT-based platforms will assume it is non-coherent. This turns out to cause a big problem for the likes of QEMU and kvmtool, which generate

By forcing on DMA API usage for ARM systems, we have inadvertently kicked open a hornets' nest in terms of cache-coherency. Namely that unless the virtio device is explicitly described as capable of coherent DMA by firmware, the DMA APIs on ARM and other DT-based platforms will assume it is non-coherent. This turns out to cause a big problem for the likes of QEMU and kvmtool, which generate

...- Syncing the Resurrection Remix's source from its repo onto my machine - Finding the make targets for building just the ramdisk instead of building the whole RR ROM which was not the goal - Finding the tool and the arguments for that to build the boot.img that can be fastboot-ed 3. Building a working kernel from source for my RR on Nexus 5, first with Android NDK r13b gcc - Finding the DirtyUnicorn kernel source, building it with gcc in the first place, generating the boot.img - Finding the right kernel config for the hammerhead kernel - uni...

...[ -f /lib/modules/`uname -r`/kernel/drivers/input/keybdev.o ] && action $"Initializing USB keyboard: " modprobe keybdev + [ -f /lib/modules/`uname -r`/kernel/drivers/input/mousedev.o ] && action $"Initializing USB mouse: " modprobe mousedev fi if [ -f /fastboot ] || grep -iq "fastboot" /proc/cmdline 2>/dev/null ; then The kernels released with RH8 include the files /lib/modules/`uname -r`/kernel/drivers/input/keybdev.o and mousedev.o - kernel 2.4.20 integrates the function of these modules into the HID module so those files aren''...

...P: Stephen Tweedie, Andrew Morton -M: sct@redhat.com, akpm@osdl.org +M: sct@redhat.com, akpm@linux-foundation.org L: linux-ext4@vger.kernel.org S: Maintained @@ -1972,7 +1972,7 @@ M: ebiederm@xmission.com W: http://www.xmission.com/~ebiederm/files/kexec/ L: linux-kernel@vger.kernel.org -L: fastboot@osdl.org +L: fastboot@lists.osdl.org S: Maintained KPROBES @@ -2310,7 +2310,7 @@ NETEM NETWORK EMULATOR P: Stephen Hemminger M: shemminger@linux-foundation.org -L: netem@osdl.org +L: netem@lists.osdl.org S: Maintained NETFILTER/IPTABLES/IPCHAINS @@ -2349,7 +2349,7 @@ NETWORK DEVICE DR...