<apritzel>
MoeIcenowy: is it known that the upper USB port on the Pine64 gives only limited performance?
<apritzel>
speaking about 4.11-rc3 here, with the MUSB driver enabled and driving the upper port
<apritzel>
I see it limited at about 18.5 MB/s (hdparm), while the other USB port gives me 20MB/s or 37 MB/s (for two different USB keys)
apritzel has quit [Ping timeout: 240 seconds]
vishnup has quit [Quit: Leaving]
vishnup has joined #linux-sunxi
<MoeIcenowy>
apritzel: yes MUSB is worse than *HCI for host.
<MoeIcenowy>
I'm now waiting for H3 USB PHY patch to be merged, then I can switch A64 MUSB to automatically select mode.
<MoeIcenowy>
s/MUSB/USB0/
Ntemis has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
<apritzel>
MoeIcenowy: ah right, I now remember there was something cooking on your side
<apritzel>
MoeIcenowy: so thanks!
<apritzel>
with 4.11-rc3, can I enable EHCI0 in the DT?
<apritzel>
(without automatic switching)
diego_r has quit [Ping timeout: 240 seconds]
<MoeIcenowy>
nope
<MoeIcenowy>
except you manually change a register in USB PHY
<apritzel>
Ah, OK, so the PHY switch resets to the MUSB?
<MoeIcenowy>
its default value is MUSB.
<apritzel>
I see
<MoeIcenowy>
and it's needed to manually switch it to *HCI.
diego_r has joined #linux-sunxi
<apritzel>
Yes, makes sense now, thanks
<apritzel>
MoeIcenowy: do you think "default y if ARCH_SUNXI" is useful in the PHY_SUN4I_USB Kconfig entry?
<MoeIcenowy>
maybe
<apritzel>
defconfig is pretty good, but lacks USB because of this
<apritzel>
I guess I just post it and see what people say
<apritzel>
and enabling MUSB in menuconfig is pretty nasty: it requires CONFIG_USB_MUSB_HDRC and CONFIG_NOP_USB_XCEIV to be selected first, before CONFIG_USB_MUSB_SUNXI even becomes visible
<apritzel>
I wonder if that should be fixed (to use "select" instead of "depends on" for those features)
vishnup has quit [Quit: Leaving]
<MoeIcenowy>
the latter one should be select
<MoeIcenowy>
but the first one... musb-sunxi is only one subfunction of musb
vishnup has joined #linux-sunxi
<apritzel>
yeah, makes sense
vishnup has quit [Remote host closed the connection]
vishnup has joined #linux-sunxi
Andy-D has quit [Ping timeout: 240 seconds]
victhor has quit [Ping timeout: 240 seconds]
chlorine has joined #linux-sunxi
chlorine has quit [Ping timeout: 260 seconds]
lkcl has quit [Ping timeout: 260 seconds]
sgteem has joined #linux-sunxi
ninolein has joined #linux-sunxi
sgteem_ has quit [Ping timeout: 264 seconds]
ninolein_ has quit [Ping timeout: 246 seconds]
cnxsoft has joined #linux-sunxi
apritzel has quit [Ping timeout: 260 seconds]
wzyy2 has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
<wens>
apritzel: would using the new imply syntax with the SoC selection work?
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-sunxi
d0m has quit [Ping timeout: 260 seconds]
reev has joined #linux-sunxi
dave0x6d has quit [Quit: Connection closed for inactivity]
chlorine has joined #linux-sunxi
chlorine has quit [Ping timeout: 260 seconds]
pg12 has quit [Ping timeout: 246 seconds]
pg12 has joined #linux-sunxi
dave0x6d has joined #linux-sunxi
terra854 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
quard has quit [Quit: Leaving]
laj has quit [Quit: Page closed]
vishnup has quit [Ping timeout: 256 seconds]
my123_ has joined #linux-sunxi
my123_ has joined #linux-sunxi
my123_ has quit [Changing host]
chlorine has joined #linux-sunxi
Putti has quit [Ping timeout: 240 seconds]
my123 has quit [Ping timeout: 240 seconds]
Putti has joined #linux-sunxi
chlorine has quit [Ping timeout: 264 seconds]
TheSeven has quit [Ping timeout: 258 seconds]
TheSeven has joined #linux-sunxi
Putti has quit [Remote host closed the connection]
Putti has joined #linux-sunxi
reinforce has joined #linux-sunxi
meridion_ has joined #linux-sunxi
mzki_ has joined #linux-sunxi
montjoie_ has joined #linux-sunxi
_hp197 has joined #linux-sunxi
GrimKriegor_ has joined #linux-sunxi
rtp_ has quit [Ping timeout: 240 seconds]
mzki has quit [Ping timeout: 240 seconds]
GrimKriegor has quit [Ping timeout: 240 seconds]
meridion has quit [Ping timeout: 240 seconds]
hp197 has quit [Ping timeout: 240 seconds]
montjoie has quit [Ping timeout: 240 seconds]
GrimKriegor_ is now known as GrimKriegor
rtp has joined #linux-sunxi
DullTube has joined #linux-sunxi
IgorPec has joined #linux-sunxi
lemonzest has joined #linux-sunxi
tkaiser has joined #linux-sunxi
paulk-collins has quit [Ping timeout: 260 seconds]
velly has joined #linux-sunxi
jernej has quit [Ping timeout: 240 seconds]
meridion_ is now known as meridion
my123_ has quit [Ping timeout: 260 seconds]
zoobab has quit [Ping timeout: 246 seconds]
zoobab has joined #linux-sunxi
Putti has quit [Ping timeout: 240 seconds]
valkyr1e has quit [Ping timeout: 240 seconds]
Putti has joined #linux-sunxi
my123 has joined #linux-sunxi
my123 has quit [Changing host]
my123 has joined #linux-sunxi
valkyr1e has joined #linux-sunxi
my123 has quit [Max SendQ exceeded]
my123 has joined #linux-sunxi
my123 has quit [Changing host]
my123 has joined #linux-sunxi
f0xx has joined #linux-sunxi
lurchi__ has joined #linux-sunxi
apritzel has joined #linux-sunxi
lkcl has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
chlorine has joined #linux-sunxi
techping has joined #linux-sunxi
chlorine has quit [Ping timeout: 268 seconds]
tkaiser has quit [Ping timeout: 256 seconds]
massi has joined #linux-sunxi
florianH has joined #linux-sunxi
cosm has quit [Remote host closed the connection]
cosm has joined #linux-sunxi
BenG83 has quit [Quit: Leaving]
tkaiser has joined #linux-sunxi
apritzel has quit [Ping timeout: 240 seconds]
paulk-collins has joined #linux-sunxi
<montjoie_>
oups, opipc TX drop to 37Mb/s, seems hitting a regression
montjoie_ is now known as montjoie
dave0x6d has quit [Quit: Connection closed for inactivity]
<KotCzarny>
and for a really cheap diy you can even get plastic standoffs
<gjm>
meh
leviathancn has joined #linux-sunxi
leviathancn has quit [Read error: Connection reset by peer]
Worf has quit [Quit: Konversation terminated!]
<KotCzarny>
another way would be redrilling M2.5 into M3 holes
leviathancn has joined #linux-sunxi
techping has quit [Remote host closed the connection]
IgorPec has quit [Ping timeout: 240 seconds]
IgorPec has joined #linux-sunxi
lamer14902637236 has joined #linux-sunxi
petard_ has joined #linux-sunxi
tkaiser has quit [Ping timeout: 240 seconds]
BenG83 has joined #linux-sunxi
<montjoie>
net-next does not like sunxi:(
<JohnDoe_71Rus>
gjm: cool things :)
leviathancn has quit [Ping timeout: 260 seconds]
Worf has joined #linux-sunxi
wzyy2 has quit [Ping timeout: 260 seconds]
enrico__ has joined #linux-sunxi
<oliv3r>
Hey all, where on the wiki/manual can i find which interrupt number is used by a peripherial. I can see it in the dtsi of course, but i'm looking for a table of sorts I suppose
<oliv3r>
or more directly, I'm seeing this occasionally in my logs: kernel: serial8250: too much work for irq48
<KotCzarny>
cat /proc/interrupts |grep 48 ?
<oliv3r>
on 4.9.13; and on our older 4.2.0-rc7 kernel I saw the same message, but for irq47. the thing is, our devicetree hasn't really changed
<oliv3r>
KotCzarny: oh that's kind of obvious too D:
<KotCzarny>
;)
<oliv3r>
anyway, i wanted to see if irq47/48 always maps to the same peripherial
<oliv3r>
or if there is some more dynamic magic happening (which I don't think)
<oliv3r>
so i still kind of need to find it from the manual :(
<oliv3r>
hmm, it does look like the old 4.2 and new 4.9 kernel have interrupts for the same devices
<oliv3r>
everything starts +1
<oliv3r>
so i guess there was a change with the (sunxi) interrupts?
<maz>
does this 47/48 appear on the left or right side of /proc/interrupts?
<oliv3r>
left
<oliv3r>
its the very first index
velly has quit [Read error: Connection reset by peer]
reev has quit [Read error: Connection reset by peer]
<maz>
if it is on the left, this is a virtual interrupt number, allocated on the fly, which has no relationship whatsoever with the HW.
<oliv3r>
ah, excellent
<maz>
if you're concerned with the GIC INTID, it is the index on the right.
fkluknav has joined #linux-sunxi
<oliv3r>
maz: thanks, now i just need to find where in the manual they list these
reev has joined #linux-sunxi
velly has joined #linux-sunxi
<oliv3r>
irq 33 seems to be rightly so 32 + 1 which is the irq for the serial port according to the dtsi
chlorine has joined #linux-sunxi
<oliv3r>
anyhow, i don't see it in the docs yet :(
chlorine has quit [Ping timeout: 240 seconds]
<KotCzarny>
page 147?
<KotCzarny>
paragraph 1.11 GIC
leviathancn has joined #linux-sunxi
wzyy2 has joined #linux-sunxi
Andy-D has joined #linux-sunxi
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 258 seconds]
libv has joined #linux-sunxi
libv_ has quit [Ping timeout: 240 seconds]
IgorPec114 has joined #linux-sunxi
LargePrime has quit [Ping timeout: 258 seconds]
leviathancn has quit [Ping timeout: 260 seconds]
chlorine has joined #linux-sunxi
chlorine has quit [Ping timeout: 260 seconds]
LargePrime has joined #linux-sunxi
lkcl has quit [Read error: Connection timed out]
<oliv3r>
a gic, of course
<oliv3r>
KotCzarny: thank you
<oliv3r>
silly me was looking for IRQ and interrupt
<oliv3r>
and i started a ctrl-f on the pdf on 'interrupt' but that was painful
lkcl has joined #linux-sunxi
petard_ has left #linux-sunxi [#linux-sunxi]
petard_ has joined #linux-sunxi
<KotCzarny>
in /proc/interrupts you had a hint ;)
<oliv3r>
yeah but I didn't even think of looking there :p
<oliv3r>
well the dts also hints it 'GIC_SPI' :)
<KotCzarny>
go for a walk, your mind needs unclogging ;)
<oliv3r>
it does
<oliv3r>
just really tired :)
libv has quit [Ping timeout: 260 seconds]
velly has quit [Ping timeout: 240 seconds]
reev has quit [Ping timeout: 240 seconds]
f0xx has quit [Ping timeout: 240 seconds]
<willmore>
KotCzarny, 3D print your cases? ;) Ask oliv3r to print you some. ;)
<KotCzarny>
:)
vagrantc has joined #linux-sunxi
<KotCzarny>
it's just a temporary measure to prevent dust/short danger
<KotCzarny>
and putting it in a full case would raise temperature significantly
<oliv3r>
i could!
<KotCzarny>
:)
<oliv3r>
willmore: how did you know?
<KotCzarny>
oliv3r: can one order custom designed ones? ;)
<oliv3r>
i dont' design :p
<KotCzarny>
then cardboard/wood/plexi/metal case is easier to make
<oliv3r>
lol
<oliv3r>
i guess :)
fkluknav has quit [Ping timeout: 260 seconds]
lkcl has quit [Read error: Connection timed out]
<KotCzarny>
would be nice to have a 3d printer using some metal as a material
<oliv3r>
yeah :(
<oliv3r>
well we have plastic mixed with metal
<oliv3r>
it feels like the real thing
<oliv3r>
and if you polish it (brass for example) even looks real
<KotCzarny>
ho, hum, interesting
<willmore>
oliv3r, you mentioned your employer and I'm a 3d printing geek, so I remembered.
<oliv3r>
willmore: ahh right-o )
<KotCzarny>
does it have em shielding properties too?
<oliv3r>
willmore: thought we may have met at FOSDEM
<oliv3r>
KotCzarny: conductivity is really bad generally; so doubt it
<KotCzarny>
pity
<willmore>
oliv3r, I hope to see some of your people at the MRRF.
<willmore>
Don't need conductivity for shielding.
<oliv3r>
willmore: yeah but that would be marketing department :)
lkcl has joined #linux-sunxi
<oliv3r>
we should run some tests to see if we could
<willmore>
Well, I'll stop by and say "Hey, say hello of oliv3r for me!"
<oliv3r>
:p
<oliv3r>
well i do know the marketing department :)
<oliv3r>
i don't know if they have plans on going to the MRRF
<willmore>
Want me to put in a good word or you? ;)
<oliv3r>
:p
<KotCzarny>
convince them that maker-people often want to talk to technical people ;)
<oliv3r>
that's why we go to FOSDEM as developers :)
<willmore>
I'm pretty sure I saw them on the list of manufacturers going. It's one of the biggest meetups, so they can hardly miss it.
<oliv3r>
then they are likley to be there
<KotCzarny>
willmore: i've thought you have to make grounded faraday cage for shielding to work
<willmore>
KotCzarny, degrees of shielding. You need perfect? Then you need a fariday cage. Need to not splatter RF all over the place? Then you don't need something that perfect.
<KotCzarny>
willmore, so what's 'good enough [tm]' solution?
<oliv3r>
for our NFC tests, we needed a solid metal encloser to silence all RF comming from the lime2
<willmore>
KotCzarny, I'm looking at conductive filaments or ones with conductive particles in them. CF is my current attempt.
<willmore>
oliv3r's application requires regulatory compliance, so is a bit more critical.
<willmore>
Plus, I'd think that your motor control board and motor wiring would be the main emitters.
<KotCzarny>
how thinck those filaments would have to be? single pencil drawing class or alu-foil class?
<KotCzarny>
*thick
<willmore>
Well, you're going to want it somewhat mechanically stable, so 2mm or 2.4mm (3x0.6mm) is reasonable. That means the bulk resistance of the material doesn't have to be all that good.
IgorPec114 has quit [Ping timeout: 264 seconds]
<willmore>
I have yet to really do much experimentation on it. I need to nuke a piece of it first. :) That's a cheap 'does it absorb RF' test.
<oliv3r>
UART_16550_COMPATIBLE=NO hmm, i wonder, if this solves my issue, why is it not the default in the sunxi_defconfig ...
massi has quit [Remote host closed the connection]
chlorine has joined #linux-sunxi
chlorine has quit [Remote host closed the connection]
chlorine has joined #linux-sunxi
jernej has joined #linux-sunxi
chlorine has quit [Remote host closed the connection]
petard_ has quit [Remote host closed the connection]
afaerber has quit [Quit: Leaving]
IgorPec has quit [Ping timeout: 260 seconds]
lemonzest has quit [Quit: Leaving]
enrico__ has quit [Quit: Bye]
IgorPec has joined #linux-sunxi
tkaiser has joined #linux-sunxi
BenG83 has joined #linux-sunxi
<tkaiser>
KotCzarny: I tried to update overview for all currently available or soon to be released H2+/H3/H5 boards: https://forum.armbian.com/index.php?/topic/1351-h3-board-buyers-guide/&do=findComment&comment=28169 (so in case you want to update wiki table ;) )
<KotCzarny>
ehehehe
<KotCzarny>
as i've said, there should be only one page for each vendor for each soc
<KotCzarny>
;)
<KotCzarny>
tkaiser: maybe just add that link to wiki page in notes/'further reading'
<tkaiser>
'One page for each vendor for each soc'? Nope, and I meant your huge and unmaintained table I don't even find in the wiki.
<tkaiser>
jernej: A good starting point for your RK3288 adventures? :)
<jernej>
Well, first adventure is already finished - creating mainline MiQi support, but that is offtopic here :)
<jernej>
I mean U-boot support
<jelle>
jernej: hmm you joined the darkside? :P
<jernej>
jelle: why darkside? Let say that I'm impressed with video/media capabilities and there is common point Synopsys DW HDMI controller, which means I can test for possible regressions during H3 driver development
<jelle>
ah also mali :(
<jernej>
True, but at least driver is available with the new license directly from ARM site
<tkaiser>
KotCzarny: Why get people excited being able to combine 1-6 pieces of spinning rust?
<jelle>
tkaiser: it loooks like 2.5"?
<KotCzarny>
i'm not excited, just noticing weird 'case'
<KotCzarny>
', as the processor was designed for low-cost 802.11ac routers' lol
<TheLinuxBug>
that is kinda sexy
<tkaiser>
jelle: Sure, 2.5". But I don't understand why people want to use 6 x 2.5" instead of 2 x 3.5" (to get back on-topic since this is possible with sunxi boards without shitty port multipliers ;) )
<TheLinuxBug>
but not big on MIPS eh
<TheLinuxBug>
but that price is way to expensive also, might as well just buy a warrented Synology system or something about the time you hit over 150$
<KotCzarny>
what port multipliers? in comments someone notices it's 3 pcie lanes (2 drives on each)
<TheLinuxBug>
um each lane has a multiplier then
<TheLinuxBug>
cause 1 lane = 1 SATA lane without a multiplier
<tkaiser>
KotCzarny: Really?
<TheLinuxBug>
so 3 lanes with multiplier for 6 total sata ports
<KotCzarny>
that's assuming you connect 6
<tkaiser>
TheLinuxBug: Nope
<TheLinuxBug>
?
<TheLinuxBug>
hmm
<TheLinuxBug>
what chipset they using for SATA Then
<TheLinuxBug>
either way it sounds like 2 drives share 1 lane
<KotCzarny>
ahm, it was tkaiser, hehe
<tkaiser>
KotCzarny: I was talking about PMs have to be used with sunxi. And if you both read the comments carefully then you get all information already ;)
<KotCzarny>
ASM1061
<TheLinuxBug>
SM1061 providing 2 SATA ports
<TheLinuxBug>
yeah isn't that a PM
<TheLinuxBug>
was looking for a card for my ESPRESSOBin and it had similar chipset and was a PM
<KotCzarny>
but if you connect only one drive instead of 2 bw wont have to be split
<tkaiser>
KotCzarny: BW is not an issue with spinning rust, especially shitty 2.5" HDDs
<KotCzarny>
yeah, shitty 2.5 ssds
<KotCzarny>
;)
<TheLinuxBug>
lol
<tkaiser>
TheLinuxBug: Nope, PCIe controllers can implement as many SATA ports as they want, no PM involved
<TheLinuxBug>
interesting
<TheLinuxBug>
I didn't know that, well or didn't understand it in that way
<TheLinuxBug>
but even without being a PM
<TheLinuxBug>
that still implies the lane is split amongst however many drives is attached to it
<TheLinuxBug>
so its not like you get 5Gbps per drive in thise case
<KotCzarny>
pcie bw is quite a lot
<TheLinuxBug>
you get that per 2 drives
<TheLinuxBug>
ohh I know
<TheLinuxBug>
especially when using only SATA II 3.0Gbps drives
<TheLinuxBug>
its more than enough
<TheLinuxBug>
just saying ;p
<tkaiser>
But back to the topic: We can use an Allwinner R40, connect 1 3.5" HDD to the SATA port, one 3.5" to an USB port, use mdraid with --write-mostly pointing to the USB disk and have something most probably outperforming this 6 port 2.5" thingie at lower costs.
<tkaiser>
So why do people get crazy when they can add many disks to one host?
<KotCzarny>
i need at least 2 sata ports, system and storage, and 1-2 more could be useful for temporary connects
<TheLinuxBug>
I do it for raid my self with larger amounts of storage
<TheLinuxBug>
actually one of the things I intend to test out for the ESPRESSObin is how efficient the raid processing is on chip
<TheLinuxBug>
currently im using a Jmicron PM behind it and its does pretty well
<TheLinuxBug>
but I want to see if I attach 5 drives raw to it what performance will be on raid5 sicne they say it has offloading for that
<TheLinuxBug>
so was considering that adapter, but probably need to do better driver research before considering a purchase
<tkaiser>
TheLinuxBug: Let's stop, it gets off-topic again. Just one note: real men don't use RAID-5 but mirrored ZFS mirrors to get also awesome random IO performance in their ZFS based redundant storage clusters ;)
rotcpy_ has quit [Quit: leaving]
rotcpy has joined #linux-sunxi
<KotCzarny>
are there any plans from xunlog regarding r40?
<tkaiser>
No idea (both regarding what Xunlong does next and R40 in general)
netlynx has quit [Quit: Ex-Chat]
<TheLinuxBug>
pft
<TheLinuxBug>
I see what you did there..
<TheLinuxBug>
maybe if I had the money for it that would be one thing
popolon has quit [Quit: WeeChat 1.7]
<TheLinuxBug>
the whole idea is to do it on the cheap eh, thus my use of arm
<TheLinuxBug>
I could of course do as I mentioned before and just buy a prebuilt solutions, but where is the fun in that :p
<tkaiser>
TheLinuxBug: Fun? RAID is not fun but crap. IMO (dealing with this stuff for over 20 years and having seen so many RAIDs failing so stupidly). And who needs this level of 'availability' at home? Think about backup, thing about snapshots, think about vacation and anything else... then thing about RAID :)
<TheLinuxBug>
erm I guess I do
<TheLinuxBug>
I have 3 different raid5 setups
<TheLinuxBug>
been very reliable for me
<TheLinuxBug>
lost first drive in 2 years a week ago and threw in a new drive and back up in working in about 8 hours no issues
<Ke>
personal experience is no match for quantitative data, that is sadly very much missing in these conversations
<Ke>
outside of quatitative data it's just aesthetics
<Ke>
mostly there is no data, I guess
<TheLinuxBug>
but my setup isn't exactly being abused 24/7 either, so yeah that will contibute to its reliability I suppose
yann-kaelig has quit [Quit: Leaving]
<TheLinuxBug>
if this was in a business and getting hit hard all the time I could see it not being the right solution
foxx has quit [Ping timeout: 240 seconds]
f0xx has quit [Ping timeout: 258 seconds]
<tkaiser>
TheLinuxBug: Last comment: Who needs 'business continuity' at home? That's all RAID is about (at least the R in RAID). And both 'hardware RAID-5' or mdraid-5 are horrible. But since we fortunately have no sunxi devices capable of this (only stupidly adding PMs) we can stop here :)
reinforce has quit [Quit: Leaving.]
<TheLinuxBug>
lol
<TheLinuxBug>
okay :)
<TheLinuxBug>
I mean I could answer you but I know its moot hehehe, so we will just leave it at that :)
Rockme has joined #linux-sunxi
IgorPec has quit [Ping timeout: 256 seconds]
<Rockme>
Hello there
<Rockme>
I'm quite a noob in embeded linux, I'm looking for a way to connect a cheap touchscreen on a Nanopi Neo. Unfortulately I've got only one HW SPI chip select, any idea how to configure a cs1 that is not originaly dedicated for it? thanks :)
<Rockme>
I cannot find any documentation about it, it seems quite easy on RPI with device tree. But I tryed the 3 main distributions and cannot make it work. Any direction to take or suitable documentation or at least keywords would be fantastic
<BenG83>
does spidev support defining additional CS in devicetree? usually I just toggle CS as GPIO
<Rockme>
No it doesnt seems to
<Rockme>
the thing is, I'm not even sure that on the dietpi distribution, the device tree is working
<Rockme>
fex script works but spi configuration in the /dietpi/config.txt do not seems to work
<Rockme>
(for the DietPi example)
<tkaiser>
Rockme: Better ask in their forum. Maybe somewhere there has any clues about kernel related stuff combined with this diet userland.
<Rockme>
You suggest DietPi forum or any other one?
<Rockme>
I was willing to do that tomorrow
<tkaiser>
Rockme: Fuzon/Fourdee/DietPi forum. But usually they don't have any clues when something is below userland level. I also heard they recently switched to Armbian's unsupported dev kernel on H3 boards but don't really care. What does an 'uname' say?
<Rockme>
ok, let me one sec
<Rockme>
thanks guys btw
<Rockme>
for instance here on DietPi: Linux DietPi 3.4.113-sun8i #10 SMP PREEMPT Thu Feb 23 19:55:00 CET 2017 armv7l GNU/Linux
<Rockme>
tkaiser: If you are right, that seems a bad news to me ...
<tkaiser>
Rockme: Ok, 'legacy' kernel so fex modifications work and device tree stuff not. But can't help further. I only know that DietPi folks use Armbian's build system, create an image, cripple it and then add the DietPi userland stuff on top of it. So really better ask in their forum :)
chlorine has joined #linux-sunxi
<Rockme>
lol ok
<Rockme>
good to know I DT do not work
<Rockme>
it is at least a beginning. I'll end up making my own module to handle that I guess...
<Rockme>
thanks for your help and redirecting me tkaiser. I'll ask on different forum if there is a solution.
chlorine has quit [Ping timeout: 256 seconds]
<tkaiser>
Rockme: You'll find a lot of SPI device related stuff searching through Armbian forum. But I don't know how much of it applies to DietPi after they let their 'prep for dietpi' script run.
<tkaiser>
Rockme: Anyway, this channel is about mainline kernel so fex related stuff with legacy kernel is considered off-topic anyway :)
<Rockme>
tkaiser: Haha, yeah but I needed a voice of true to redirect me ;) Thanks for the help. </off-topic>