Re: [opensuse-arm] Booting Tumbleweed in qemu?

in qemu? I had no trouble "running" Aarch64 Tumbleweed with qemu-aarch64, just installed it from virt-manager. Due to full emulation, it is somewhat slow, though. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 15

Re: [opensuse-arm] unicam driver for rpi?

tps://lwn.net/ml/linux-media/20200424013419.12954-1-laurent.pinchart@ideas > onboard.com/ Not a direct answer to your question, but for HDMI input I currently use one of the cheap (~20€) HDMI-to-USB-2.0 dongles which started to appear a few months ago. Works out-of-the-box as these are UVC compliant. Kind re

Re: [opensuse-arm] rpi to rpi via usb gadget (WORKS!)

On Dienstag, 8. September 2020 17:52:17 CEST Ludwig Nussel wrote: > Stefan Brüns wrote: > > On Freitag, 4. September 2020 17:43:37 CEST Ludwig Nussel wrote: > >> Stefan Brüns wrote: > >>> On Freitag, 4. September 2020 14:25:37 CEST Ludwig Nussel wrote: > >>&g

Re: [opensuse-arm] rpi to rpi via usb gadget

On Montag, 7. September 2020 17:34:19 CEST Ludwig Nussel wrote: > Stefan Brüns wrote: > > [...] > > requesttype: 0x21 - Class specific request to interface > > request: 0xA - Set_Idle > > > value: 0xA00 - 0xA * 4ms = 40ms report interval during idle, 0x0: &

Re: [opensuse-arm] rpi to rpi via usb gadget

On Montag, 7. September 2020 10:52:51 CEST Ludwig Nussel wrote: > Stefan Brüns wrote: > > [...] > > You may try this patch: > > https://build.opensuse.org/package/view_file/ > > home:StefanBruens:branches:hardware:boot/u-boot/0001-usb-kbd-Also-accept- > > keybo

Re: [opensuse-arm] rpi to rpi via usb gadget

single protocol. An interface typically shows up as a single device in Linux. That said, though there is no causal relationship between multiple interfaces and existence of an interrupt OUT endpoint, there may be a tendency of more complex devices to have it. Kind regards, Stefan -- Stefan Brü

Re: [opensuse-arm] rpi to rpi via usb gadget

On Freitag, 4. September 2020 17:43:37 CEST Ludwig Nussel wrote: > Stefan Brüns wrote: > > On Freitag, 4. September 2020 14:25:37 CEST Ludwig Nussel wrote: > >> Fabian Vogt wrote: > >> to get rid of the otg descriptor. That's not the issue though. > >> I fo

Re: [opensuse-arm] rpi to rpi via usb gadget

re unlikely. Does the OTG device only emulate an USB Keyboard (Class/Subclass/Protocol: 3/1/1), or also a mouse (3/1/2)? U-Boot might be confused when a device has interfaces with both protocols. Other than that, I fear you either have to recompile U-Boot with additional debug output, or connect

Re: [opensuse-arm] rpi2 does not boot after update to ARM Tumbleweed snapshot 20200226

2 image from [2] and it does not boot > either! > Matthias, Nicolas, any idea what is wrong with latest DTBs? > Maybe DTB from 5.5 branch is not working with RPi2 and/or older kernels? Guillaume, can you compare the two DTs with dtdiff, part of dtc? Kind regards, Stefan -- Stefan Brün

Re: [opensuse-arm] Pimoroni pHAT DAC on Raspberry Pi 3

verlay contents, look for the hifiberry-dac- overlay.dts Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

Re: [opensuse-arm] Raspberry Pi 4 Model B

ications to take > > into account. > > Correct. And the security implications make me very nervous. That > direction is not tested or spoofed for security. > > Regards > Oliver Can someone please outline what these security implications are? 1. Without

Re: [opensuse-arm] Open SuSE on Beagleboard X15

On Sonntag, 7. April 2019 21:40:14 CEST you wrote: > > Le 7 avr. 2019 à 15:16, Stefan Brüns a > > écrit :> > > On Sonntag, 7. April 2019 19:56:52 CEST Michel Catudal wrote: > >> I have Funtoo, Gentoo, Arch Linux, Fedora, SuSE and Slackware working on > >>

Re: [opensuse-arm] Open SuSE on Beagleboard X15

), XFCE, LXQT, KDE, ... Have a look at the "JeOS" project in the OBS. For the predecessor, Beagleboard xM, there is an image, see https:// en.opensuse.org/HCL:BeagleBoard-xM Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49

Re: [opensuse-arm] Raspberry Pi 3 B+ ?

. I have some Pine64 here, RPIs, an RK3399 STB. Raspbian would be able to run on one of these ... Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

Re: [opensuse-arm] Raspi Update of Leap 15: DNS broken

nothing with 7515 to > > grep in the output. lsusb strings may be wrong if the value is taken from the usb.ids table and not the device itself. AFAIK SMSC/Microchip uses the chip name as product id, i.e. 0x9512, 0x9514, 0x7515. Vendor/product ID are shown in lsusb as :. > Updat

Re: [opensuse-arm] Images for Banana Pi M3 available?

you data center). The userland is the same for all boards with a common architecture, but 32 and 64 bit ARM are different. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally

Re: [opensuse-arm] http://download.opensuse.org/ports/aarch64/debug/tumbleweed is missing

sue is somewhat annoying - I am trying to debug a crash, and now I have to hunt down every single debuginfo/debugsource package from the buildservice. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Descript

Re: [opensuse-arm] Out of memory problems with AArch64 workers

/build.opensuse.org/package/live_build_log/home:Guillaume_G:branches: > openSUSE:Factory:ARM/JeOS:JeOS-efi-devel.aarch64/images/aarch64 9 + 2 GByte, again xsltproc runs out of memory. My assumption is either a bug in xsltproc, or the processed files somehow generate an infinite loop. C

Re: [opensuse-arm] RPi 3 video requires CMA memory which is not automatically configures

it as a gaming console and need 256 MB. Contrary to other current systems, the memory has to be contigous and can not be freed after allocation. > So yes, I insist that the buffer for the IGP is allocated even in the > case there is no proprietary BIOS and there is only opensource

Re: [opensuse-arm] Packet fake-hwclock generated

*once*, as timesyncd would be stopped before ntpd has locked. Stefan > Am 18.12.2017 um 09:34 schrieb Stefan Brüns: > > On Monday, December 18, 2017 8:58:31 AM CET BWC Illmensee GmbH - Ralph > > Gauer> > > wrote: > >> systemd-timesyncd conflicts with ntp

Re: [opensuse-arm] Packet fake-hwclock generated

> Not that I am aware off. I only did some basic installation stuff. > >> Did enable > >> systemd-timesyncd.service, even started it, but after a reboot the > >> date/time > >> only changes after NTP becomes active. > >> /etc/fstab looks like follows: > >> /dev/disk/by-id/mmc-SD08G_0x7c498e75-part2 / ext4 noatime,nobarrier 1 1 > >> /dev/disk/by-id/mmc-SD08G_0x7c498e75-part1 /boot/efi vfat defaults 0 0 > >> /dev/disk/by-id/mmc-SD08G_0x7c498e75-part3 swap swap defaults 0 0 > >> Command mount shows for / > >> /dev/mmcblk0p2 on / type ext4 (rw,noatime,nobarrier,data=ordered) -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] No DMA on Raspberry Pi 3B using latest image

bleweed/images - and - https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/ RaspberryPi3/standard/ for building the image, although it does not add the second to the zypper repos. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

Re: [opensuse-arm] [aarch64] TW on Pinebook?

ia DHCP, and you should be able to ssh into it (login/pw: root/linux or linux/ linux). Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

Re: [opensuse-arm] [aarch64] TW on Pinebook?

sted-firmware isn't in > Tumbleweed yet? Sorry but I missed any previous discussion on ATF. At least for the Pine64 (which the Pinebook is based on) the ATF is a fork of the upstream ATF ... Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

Re: [opensuse-arm] Fail with openSUSE JeOS pine 64 image

sunxi64 already contains a fix from the sunxi kernel tree, expected for the 4.15 release. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

Re: [opensuse-arm] Packet fake-hwclock generated

atectl. The timestamp file is also saved when timesyncd is stopped, i.e. on system shutdown. Contrary to the fake-hwclock script, it does not spawn external processes on each update, and it does not write the timestamp to the file but just uses the mtime inode field, so less writes on each update. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

[opensuse-arm] Re: [opensuse-factory] New Tumbleweed snapshot 20171120 released!

https://build.opensuse.org/package/binaries/ home:StefanBruens:branches:devel:ARM:Factory:Contrib:Pine64/kernel-sunxi64? repository=standard You still need to add "sunxi-rsb axp20x-regulator axp20x-rsb" to add_drivers. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.

[opensuse-arm] Moving SoC specific files from JeOS/KIWI config.sh to separate packages

and arndale differs [2] contents of raspberrypi_modules.conf for rpi1/rpi2/rpi3 differs -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 signature.asc Description: This is a digitally signed message part.