victhor has quit [Remote host closed the connection]
yangxuan has joined #linux-sunxi
chewitt has joined #linux-sunxi
leviathan has joined #linux-sunxi
yangxuan has quit [Ping timeout: 268 seconds]
dddddd has quit [Remote host closed the connection]
yangxuan has joined #linux-sunxi
yangxuan has quit [Ping timeout: 246 seconds]
yangxuan has joined #linux-sunxi
<Kamilion>
Hm, on my SOIC flasher project, what is a better choice to use as a platform to run 'flashrom' from, the H2, H3, or H5? Looking at the smaller HDMIless orange pi range.
<Kamilion>
i've been using an original "ODROID-C" with the S805 (think it's referred to as the C1 now) for a long time, think it's about time to move to something smaller.
<Kamilion>
I was thinking about the C0 board, but at $28/ea I figured the orange pis would be a better deal.
<Kamilion>
I really like the Orange Pi Lite 2, but I've had them sidelined for months waiting for mainline
<smaeul>
are you planning to do any hardware modifications, like soldering pins or SPI flash to boot from?
<smaeul>
generally h2/h3 boards are going to be a bit cheaper, and 64-bit doesn't mean much for flashrom
<Kamilion>
that's an ESP32 board; but I'm having troubles getting various vendor parts unlocked/writable
<Kamilion>
works on the odroid
<Kamilion>
was more curious how well the SPI bus performance was doing at the moment between the H2+/H3 and the H5, which seems to have gotten devicetree entries added much later.
<Kamilion>
and if I was gonna run into anything major with the H5 that I wouldn't on the H2+/H3
<smaeul>
I've found SPI on the H5 very solid, much more reliable than e.g. a raspi
<Kamilion>
i'll go with the Orange Pi Zero Plus / H5 / 512MB then, since I'd prefer the gigabit ethernet MAC. I think the only thing I lose is the potential of the PoE breakout on the H2+ board.
<smaeul>
it's not real PoE anyway. it's just "5v over UTP"
<Kamilion>
yeah
<Kamilion>
Thanks a bunch. I was leaning towards the headless H5 anyway.
<Kamilion>
otherwise I would have just ordered more of them
<Kamilion>
can always find a use for a USB3 host *chuckles*
<smaeul>
zero+ comes with 2MiB flash, which probably isn't enough to run your SOIC flasher project out of, but you could replace with a bigger chip
<Kamilion>
no need, uboot's enough
<Kamilion>
it suppors wireless, right?
<Kamilion>
I can get my kernel and initramfs from the network.
<Kamilion>
worse case; mount a microsd.
<smaeul>
the board supports wireless, yes, but u-boot doesn't
<Kamilion>
the BIOS images are 16MiB and 32MiB, and I've got half a gigabyte of 'em, so unless I stuck some fancy 8SOIC NAND package in, I'd need more storage anyhow.
<Kamilion>
Aw.
<Kamilion>
Oh well, I'll put some samsung or sandisk microsds in the shopping cart then.
<Kamilion>
offhand, you know the current consumption of a headless H5?
<Kamilion>
figure somewhere below 500mA since I've seen people playing with them via OTG
<smaeul>
you could boot usb or ethernet though -- I like to have a usb<->sata adapter with a cheap ssd for usecases with a lot of disk access
<smaeul>
Kamilion: idle consumption should be around 200mA
<Kamilion>
yeah, that's one of my usecases for the H6, we wipe a lot of disks here
<Kamilion>
and I want to use the UASP + H6 to do it faster and cheaper
<Kamilion>
ATA Secure Erase and Mass Storage Class don't get along :<
<Kamilion>
i know I don't need a USB3 host to use a UASP device though.
<Kamilion>
just means I can toss a bunch of drives behind a usb3 hub and blow 'em all away
<Jetfire>
plaes: I'm not sure tbh, I'm helping out someone else with a project, but I can't seem to compile anything on my system and will have to do a fresh install
<plaes>
there's also a binary of this file under bin directory
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
<Jetfire>
plaes: Thanks. I'm not sure if that will help or not. I need to change the dram and register values and uboot in the fes1.bin img we have now, so I need to make the changes and repack it, but will have to try another build of linux as this one is not compatible.
<plaes>
well, if you write this file to sd-card and reset the device, it either starts in fel mode or not
<plaes>
simple check
<Jetfire>
plaes: ok, great, thanks for the info/help. That's at least a start.
f0xx has quit [Ping timeout: 252 seconds]
selfbg has joined #linux-sunxi
<BenG83>
based on Yong´s work for the parallel CSI driver, is a MIPI CSI driver a completely new effort or can some of the work be reused/extended?
<willmore>
Kamilion, have you used one of those USB3<>SATA converters from ali that yo link to?
<willmore>
I've had trouble with such converters talking to ODDs, but that one says that they specifically support them. I'd love to see that verified before I buy a bunch. :)
<BenG83>
also does anyone know if the MIPI-CSI block is some 3rd party IP? like the Cadence CSI interface?
<plaes>
I guess you can check by comparing register layouts
<BenG83>
I have to dig up the BSP driver for that since MIPI-CSI is not documented in the datasheets I guess
<BenG83>
an hope it´s not obfuscated :)
<plaes>
csi is now merged?
<BenG83>
I don´t think so
<plaes>
I saw that patches went out few days ago
<BenG83>
I was just wondering how much work it is to extend the parallel CSI driver
<BenG83>
or if MIPI-CSI has to be done from scratch
<BenG83>
seeing that parallel CSI took 1.5 years
kaspter has quit [Remote host closed the connection]
<duncan^>
hmm.. does anyone know anything about these lichee pi zero boards?
<duncan^>
There appears to be the original lichee pi zero which is sold on taobao etc. This is a plug-in module to a bigger board with breakouts etc
<duncan^>
But on Aliexpress there is a board being sold under the name which is the same, except it's on one board, and the headphone jack and the cap are switched round
<duncan^>
so I guess there are two possiblities; it's a direct copy of the board but made cheaper on account of it on a single board, or it's a new revision of the board on a single board.
<duncan^>
I guess they're not mutually exclusive possibilities either
<plaes>
no clue, I actually backed them, but never received my stuff :S
<BenG>
I have three of the original ones
<BenG>
they more or less work as intended
<BenG>
I got mine from the indiegogo campaign
<plaes>
yeah, I backed the same campaign
<plaes>
but still waiting for my HW :)
<BenG>
I backed the wifi package
<plaes>
one of them was with the LVDS screen
<BenG>
so I got the board plus the little wifi modules
yangxuan_ has quit [Remote host closed the connection]
yangxuan_ has joined #linux-sunxi
terra854 has quit [Quit: Connection closed for inactivity]
msimpson has quit [Quit: Leaving]
hitech95_ROG has quit [Ping timeout: 244 seconds]
Andy-D has quit [Ping timeout: 240 seconds]
Andy-D has joined #linux-sunxi
afaerber has quit [Ping timeout: 250 seconds]
arete74 has quit [Ping timeout: 272 seconds]
arete74 has joined #linux-sunxi
afaerber has joined #linux-sunxi
jelly is now known as khajiit
khajiit is now known as jelly
matthias_bgg has quit [Quit: Leaving]
leviathan has quit [Remote host closed the connection]
tnovotny has quit [Quit: Leaving]
jbrown has quit [Ping timeout: 252 seconds]
TheSeven has joined #linux-sunxi
yangxuan_ has quit [Quit: Leaving]
ricardocrudo has quit [Remote host closed the connection]
m4ssi has quit [Remote host closed the connection]
jbrown has joined #linux-sunxi
lynxis_ has quit [Quit: beaming to the mars]
lynxis has joined #linux-sunxi
Gerwin_J has quit [Ping timeout: 264 seconds]
<karlp>
Kamilion: the wireless on the zero plus is full of fail unfortunately. it sort of works with the orangepi provided ubuntu image, but the one linked from http://linux-sunxi.org/Wifi#RTL8189FTV is pretty failful.
<heatfanjohn>
anarsoul: Success! Using your kernel and sightly modified config I got gdm to start and I can now remotely launch X sessions!
<anarsoul|2>
heatfanjohn: cool
<anarsoul|2>
congrats
<heatfanjohn>
I don't know if my modifications to your config were required. I changed your SUN4I-DRM tags from "y" to "m" so I could try to load the modules individually and the resulting kernel worked. It could just be a coincidence.
<heatfanjohn>
The only error message I get now is not loading /usr/lib64/dri/sun4i-drm_dri.so and then later Failed to initialize glamor, falling back to sw
<buZz>
did you install the modules you compiled after that aswell?
<buZz>
make modules_install
<buZz>
(just a hunch)
<heatfanjohn>
I did discover that U-Boot does not like the symbolic link from /boot/dtb to the required dtb directory to be an absolute link ... U-Boot started throwing all sorts of invalid file system errors
<heatfanjohn>
buZz: I might have missed doing a `make modules`
<heatfanjohn>
I redo that
<buZz>
heatfanjohn: ah :) that could be it aswell
<buZz>
make modules modules_install
<buZz>
i think modules_install always pull in 'modules' aswell
<BenG>
should I make new pages/columns for S3 or just put everything under V3s ?
<BenG>
in the wiki
jbrown has quit [Ping timeout: 252 seconds]
jbrown has joined #linux-sunxi
Putti has joined #linux-sunxi
xes has joined #linux-sunxi
jtf has left #linux-sunxi ["WeeChat 2.2"]
lkcl has quit [Read error: Connection reset by peer]
chrisf_ has joined #linux-sunxi
<heatfanjohn>
I found a Mesa patch that says sun4i-drm_dri.so is a part of Mesa and was committed in 17.2 - I don't understand why this so isn't in package mesa-dri-drivers
<anarsoul|2>
mesa doesn't support hw accell on your platform yet
Andy-D has joined #linux-sunxi
lkcl has joined #linux-sunxi
nuuuciano has joined #linux-sunxi
nuuuciano has quit [Ping timeout: 240 seconds]
<Kamilion>
karlp: thanks for the heads up, I'll stick to gigabit.
<karlp>
I-d really like them to make one with the ap6212 like they have on someo of their other boards
<karlp>
itð's much better supported.
<karlp>
can't have it all :)
<karlp>
I'd definitely prefer them to just use one wifi chip that worked on all their boards for wifi though, not the current schizophrenci combination of xr819, rtl8189ftv/etv _and_ ap6212 modules
<karlp>
or even just one of the well tested/known usb modules, there's enough spare usb host ports unused...
<karlp>
annnnyway
BenG has quit [Quit: Leaving]
Putti has quit [Ping timeout: 244 seconds]
BenG83 has joined #linux-sunxi
<Kamilion>
Eh, I've got lots of ESP32 boards; and someone wrote a kernel driver for 'em less than half a year ago
<Kamilion>
and worst case I can just hand it a USB wifi dongle
<Kamilion>
I've got a huge amount of minipcie radios, but most of 'em are unlabeled.
<Kamilion>
place I work for in california does WEEE processing for european companies; I get a lot of neat "junk" out of it
return0e_ has quit [Remote host closed the connection]
return0e has joined #linux-sunxi
netlynx has quit [Quit: Ex-Chat]
<karlp>
if I'm just going to have to add wireless to it anyway, I'd rather they didn't put it on the board
dddddd has joined #linux-sunxi
<kilobyte>
any idea if A64 (got Pine64 and a Pinebook) is supposed to handle HDMI 1.4 (needed for 2560x1600)?
<anarsoul|2>
kilobyte: it works for me in 2560x1440
<anarsoul|2>
not sure about HDMI 1.4 though
LargePrime has joined #linux-sunxi
<kilobyte>
anarsoul|2: the monitor has a DVI connector, dual-link (both 3x4 sets of pins) (and DP, but that's unrelated). Both cables I tried also have pins for dual link on the DVI side, ordinary looking HDMI on the other.
<anarsoul|2>
kilobyte: well, I don't have 2560x1600 monitor to test
jbmorley13 has joined #linux-sunxi
<anarsoul|2>
my 2560x1440 monitor uses HDMI connector
jbmorley13 has quit [Remote host closed the connection]
t0dd1v has joined #linux-sunxi
<kilobyte>
I read that HDMI 1.3 can do up to 2560x1440, 1.4 up to 2560x1600
<BenG83>
I don't know what it really does, but the BSP driver had a
<BenG83>
disp_dvi_compat=1
<BenG83>
option in the fex
<BenG83>
that makes most HDMI-to-DVI adapters work
<BenG83>
if test "${disp_dvi_compat}" = "on"; then
<BenG83>
fdt set /soc@01c00000/hdmi@01ee0000 hdmi_hdcp_enable "<0x00000000>"
<BenG83>
seems it disables HDCP on DVI links
<anarsoul|2>
I don't think we have HDCP in mainline
<BenG83>
that was my next question ;)
<BenG83>
that goes straight into the libhdmi blob I think
<BenG83>
ret = disp_sys_script_get_item("hdmi", "hdmi_hdcp_enable", &value, 1);
<BenG83>
}
<BenG83>
hdmi_core_set_hdcp_enable(value);
<BenG83>
if (1 == ret) {
reinforce has quit [Quit: Leaving.]
hitech95_ROG has joined #linux-sunxi
Kwiboo has quit [Ping timeout: 268 seconds]
lurchi__ has quit [Ping timeout: 268 seconds]
<karlp>
hrm, duo2 with some norflashsoldered down might be super.
lurchi__ has joined #linux-sunxi
<kilobyte>
farthest I get is text on green lined background (not clear enough to see if it's 1280x800, the monitor's fallback mode) during u-boot, then nothing once the kernel takes over
<kilobyte>
not even get-edid works
<kilobyte>
HDMI work being really new -- I'm using icenowy's tree atop v4.19.0, is there anything better?
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 244 seconds]
<anarsoul|2>
kilobyte: ask jernej
<kilobyte>
sounds good; he's on this channel but it's midnight in his timezone
<anarsoul|2>
yeah
<anarsoul|2>
so you'll have to wait to ask him
<kilobyte>
nothing but blackness on BSP
<kilobyte>
(not a regression compared to my other monitors -- they're all 1280x1024 which SoCs I own notoriously hate; this includes not only Allwinners but also Exynos and Mediatek)