<montjoie>
replace init content by a shell script which debug-echo all necessary stuff for runing init
<montjoie>
hanetzer: could you paste the console output ?
<montjoie>
note that my personnal lab is still not connected to kernelci but it should be soon
<montjoie>
plaes: a20 in my lab and seatle, a10 only in our seatle lab
<plaes>
montjoie: do you have a10/a20 devices in your lab?
<montjoie>
note that there will be an h6 board in our kernelci lab in some days/week
2019-01-11
<montjoie>
just in case, I have released my helper script for testing my drivers (and also building and booting linux on lots of targets) https://github.com/montjoie/bbci any comment welcome
2019-01-09
<hanetzer>
montjoie: as in, not persuing it? its mostly because I'm a bit embroiled with rockchip stuff atm (u-boot for the rk3288 veyron-speedy chromebook and acquiring a rk3399 samsung chromebook plus for u-boot, and mali work on both), I don't have time for yet another SoC in my life :P
<hanetzer>
montjoie: hmm?
<montjoie>
hanetzer: it is the better route:D!
<hanetzer>
montjoie: very true. I've went ahead and gone gentoo route
<montjoie>
hanetzer: there are no good suggestions without some needs/goal
2018-12-21
<MoeIcenowy>
montjoie: I tried to let a Banana Pi M2+ to work with fixed link ;-)
<montjoie>
MoeIcenowy: I do not have any board with fixedlink, so hard to work on this
<MoeIcenowy>
montjoie: I realized a problem that a MDIO mux is not the best way to represent the mux on H3
2018-12-06
<montjoie>
crmingle: ask your final question just in case
2018-12-01
<jernej>
montjoie: bisect came up by commit a66d972465d15b1d89281258805eb8b47d66bd36, but if I revert it, it doesn't help
<montjoie>
but got random memory problem
<montjoie>
I ran next 2 or 3 days ago
<jernej>
montjoie: Kernel prints "Starting Linux kernel" on uart and nothing more
<montjoie>
jernej: symptom ?
2018-11-29
<montjoie>
how do you trust kernel from people doing RSA in CBC mode
<montjoie>
always use the mainline!
2018-11-28
<montjoie>
not sure if it is on a64 or another one
<montjoie>
jaganteki: hit it also
2018-11-16
<montjoie>
but mripard will confirm if it is know or not for sun4i_drm_hdmi
<montjoie>
seems lots of things imbricated
<montjoie>
at least on meson drm, its maintainer said "it's complicated to fix it"
<montjoie>
karlp: could you recompile your kernel with a patch ?
<montjoie>
dont know
<montjoie>
probably it's busybox ip and not iproute2
<karlp>
montjoie: ip maddress? ip address I pasted earlier, just 1 v4 plus 2 v6
<montjoie>
I kill my enemies by making them watching old strange movies, this morning a coworker said she like Sean Connery, tonight she will see zardoz as I suggested
<montjoie>
ah ah I am a troll hunter, to be sure to remain the only one
<willmore>
Okay, I used to like you, montjoie . :P
<montjoie>
#likesystemd (troll sorry)
<montjoie>
my previous jobs, network guys had a megaphone for "not network fault"
<KotCzarny>
montjoie: you still can make some docs, it might be often asked
<montjoie>
taking coworkers by surprise
<montjoie>
now I can ran in the office yelling "ah ah not a bug"
<megi>
montjoie: I had > 8 link entries there :), I see the limit in the driver is 8 addresses
<montjoie>
could yo paste ip maddress
<KotCzarny>
karlp, there is a possibility driver still needs fixing some bug, talk to montjoie
<megi>
montjoie: ip output looks quite regular, and I have default config with one IPv4 address and one IPv6 address
<montjoie>
so it is usefull to have an "ip a" output
<montjoie>
perhaps you have lots of multicast and or ipv6 spetial address
<montjoie>
Too many address mean too many mac address in the filter list
<montjoie>
whats 's the ip a output
2018-08-30
<montjoie>
last obstable for shipit is ipsec testing
<montjoie>
cool no more luks crash with sun8i-ce
2018-08-13
<montjoie>
wens: still no answer for a new bpi-m3 on my side:( but at least the problem is fixed now
2018-08-12
<montjoie>
input/output error on any read/write on mmc
<montjoie>
got the same on R40
<montjoie>
did someone hit some mmc error with H3 on linux-next ?
2018-08-09
<rex>
hey montjoie, once my new display is here, I will try your branch. atm I won't be able to reboot, once I shut it down, cause I have no display :(
<montjoie>
so yes all classic make options exists
<montjoie>
rex: its a linux-next + patches
<montjoie>
yes
<montjoie>
you can try my crypto wip branch on github
<montjoie>
yes (shame)
<montjoie>
all kernel test pass, but when doing any action after mouting a luks partition...
<montjoie>
I have a crash when using cryptsetup
<montjoie>
rex: yes
<rex>
montjoie: Aren't you working on the crypto part?
2018-07-26
<libv>
montjoie: we are looking at just over half a TB
<montjoie>
size ?
<montjoie>
libv: If volumetry can fit on my server
<montjoie>
do you know data size and access volumetry ?
<libv>
montjoie: i would then also want to get rid of both the expense and the legal liability of this machine
<montjoie>
I have already proposed to do the sysadmin task for it
<montjoie>
and also MoeIcenowy
<montjoie>
could you set wens and mripard as ops ?
2018-07-23
<montjoie>
or wait for H7 ?
<montjoie>
MoeIcenowy: I was just trolling... my ":D" seems not enough
<montjoie>
I hoped that something different exists (like smartctl for hdd)
<montjoie>
but I seek also anything which can make proof that mmc work
<montjoie>
I will
<montjoie>
system unusable after so I dont know if something is printed, but I least I want to activate it
<montjoie>
detect it automaicly
<montjoie>
I have uptime+60s problem with mmc on linux-next, and I want to detect it
<MoeIcenowy>
montjoie: make a SDIO card ;-)
<montjoie>
nothing wrong, I want something more/different
<montjoie>
appart from "try to read with dd", any idea on how to test if mmc driver work ? (non destructive way)
2018-07-20
<willmore>
montjoie, which ATM? Automated Teller Machines or Asynchronous Transfer Mode? Is the old floppy code beautiful? The controller and hardware sure weren't.
<montjoie>
or some old ATM devices
<montjoie>
willmore: for beautifullness, did you check some old code from device nobody uses ? (just floppy for example)
2018-07-19
<montjoie>
berlin ahci is 0xe90000 0x1000 and sataphy is 0xe900a0 0x200
<montjoie>
wens: like berlin with a subaddress space
<montjoie>
MoeIcenowy: you are right, since some PHY code is used, it will be easier to create a sata phy driver
<montjoie>
MoeIcenowy: I have created a fake PHY and I will ask for advice phy people
<MoeIcenowy>
montjoie: I suggest you make a new phy driver
2018-07-18
<montjoie>
MoeIcenowy: instead of adding more code to ahci for phy, I have modelled a fake phy and use already existing phy-supply. But since the phy need to load, a fake-phy compatible (and fake driver) is needed. What do you think about it ?
<[TheBug]>
montjoie: e-mail FriendlyElec about it - I will say this - their sales team usually replies pretty quickly, however, I previously wasn't able to resolve the fact that my order had a wrong case included and I asked them to ship the right one and they just ignored me -- however, one would hope that if they shipped the wrong board they would correct that.
<montjoie>
I stuck board in the wood (via M3 screw)
<montjoie>
and board are not enough stuck to the ground
<montjoie>
hello my friendly elec nanopi neo plus2 only have 512M of RAM but the product is branded as 1G. What can I do ? Someone here asked for RAM photo http://kernel.montjoie.ovh/P1090352.JPG