Turl changed the topic of #linux-sunxi to: Allwinner/sunxi /development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi
cptG_ has joined #linux-sunxi
akaizen has quit []
cptG has quit [Ping timeout: 246 seconds]
akaizen has joined #linux-sunxi
premoboss has quit [Quit: Sto andando via]
Ueno_Otoko has joined #linux-sunxi
viccuad has quit [Ping timeout: 260 seconds]
ricardocrudo has quit [Ping timeout: 272 seconds]
<wens> ssvb: i finished my code; will test today
cnxsoft has joined #linux-sunxi
vagrantc has joined #linux-sunxi
vagrantc has quit [Changing host]
vagrantc has joined #linux-sunxi
ninolein has quit [Ping timeout: 260 seconds]
ninolein has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
dlan has quit [Quit: leaving]
MTO has quit [Ping timeout: 260 seconds]
MTO has joined #linux-sunxi
afaerber_ has quit [Ping timeout: 240 seconds]
MTO has left #linux-sunxi [#linux-sunxi]
afaerber_ has joined #linux-sunxi
dlan has joined #linux-sunxi
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
Ueno_Otoko has quit [Remote host closed the connection]
cnxsoft has quit [Quit: cnxsoft]
avph has quit [Ping timeout: 255 seconds]
cnxsoft has joined #linux-sunxi
avph has joined #linux-sunxi
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
cosm has quit [Ping timeout: 246 seconds]
HeavyMetal has quit [Quit: BNC Services Provided by the ASoTnet IRC Network.]
gzamboni has quit [Ping timeout: 246 seconds]
HeavyMetal has joined #linux-sunxi
HeavyMetal has quit [Changing host]
HeavyMetal has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 240 seconds]
p1u3sch1 has joined #linux-sunxi
TheSeven has quit [Ping timeout: 250 seconds]
TheSeven has joined #linux-sunxi
Seppoz has joined #linux-sunxi
IgorPec has joined #linux-sunxi
bonbons has quit [Quit: Leaving]
IgorPec has quit [Ping timeout: 246 seconds]
Ueno_Otoko has joined #linux-sunxi
fl_0 has quit [Ping timeout: 260 seconds]
fl_0 has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 260 seconds]
hipboi has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
HeHoPMaJIeH has joined #linux-sunxi
HeHoPMaJIeH has quit [Changing host]
HeHoPMaJIeH has joined #linux-sunxi
yann|work has joined #linux-sunxi
yann|work has quit [Ping timeout: 240 seconds]
hipboi_ has joined #linux-sunxi
hipboi has quit [Ping timeout: 276 seconds]
soderstrom has joined #linux-sunxi
<wens> orange pi one?
domidumont has joined #linux-sunxi
IgorPec has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
<KotCzarny> seriously, why the heck there is no 3.5mm audio jack on A20-OLINUXINO-LIME2
_massi has joined #linux-sunxi
arossdotme has quit [Quit: Ex-Chat]
gzamboni has joined #linux-sunxi
FlorianH has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
Gerwin_J has quit [Client Quit]
IgorPec has quit [Quit: Nettalk6 - www.ntalk.de]
yann|work has joined #linux-sunxi
hipboi_ has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-sunxi
<wens> mripard: sun50i... oh my
maz__ has joined #linux-sunxi
maz__ is now known as maz_
lemonzest has joined #linux-sunxi
<mripard> wens: hey, don't shoot the messenger :)
mawe242 has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
<plaes> :)
HeHoPMaJIeH has quit [Read error: Connection reset by peer]
_stephan has joined #linux-sunxi
afaerber_ is now known as afaerber
Ueno_Otoko has quit [Ping timeout: 260 seconds]
IgorPec has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
mosterta has joined #linux-sunxi
avph has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
fl_0 has quit [Ping timeout: 260 seconds]
fl_0 has joined #linux-sunxi
leio has quit [Ping timeout: 265 seconds]
jinzo has joined #linux-sunxi
leio has joined #linux-sunxi
formruga has joined #linux-sunxi
lemonzest has quit [Quit: Leaving]
apritzel has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 255 seconds]
iamfrankenstein1 is now known as iamfrankenstein
Ueno_Otoko has joined #linux-sunxi
viccuad has joined #linux-sunxi
SadSmile has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 265 seconds]
viccuad has quit [Quit: WeeChat 1.3]
viccuad has joined #linux-sunxi
premoboss has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
<MoeIcenowy> Anyone with a H3 here?
<MoeIcenowy> Do the official Linux distro of H3 supports mali binary driver?
<plaes> what of official linux distro?
tkaiser has joined #linux-sunxi
<tkaiser> MoeIcenowy: Forget about 'official' ones from Xunlong. There are some distros provided by community members.
<tkaiser> If patience is your strength then try to have a look at: http://www.orangepi.org/orangepibbsen/forum.php?mod=forumdisplay&fid=90
<MoeIcenowy> tkaiser: In fact I have no H3 devices
<MoeIcenowy> but I have an A33 one
<MoeIcenowy> and I succeeded to run mali binary driver on it
<MoeIcenowy> Here's r4p0 binary?!
<tkaiser> I hate this forum. It's so slow. Please do a google search for 'glmark2 r4p0 jacer gpu site:orangepi.org'
<tkaiser> IIRC there's an image from this jacer guy containing these binaries.
<MoeIcenowy> tkaiser: I don't think it slow
<MoeIcenowy> I'm in PRC
<tkaiser> Ok, then GFW again? For me it's close to unuseable most of the times.
<rellla> tkaiser: it's unuseable.
<tkaiser> rellla: What? Jacer's image? The forum?
<MoeIcenowy> Who's jacer?
<MoeIcenowy> Why can he get the binary driver?
<rellla> the forum.
<MoeIcenowy> Here's a link
<MoeIcenowy> in Baidu Pan
<MoeIcenowy> If only you can access it
<tkaiser> MoeIcenowy: Jacer is someone from PCR with good relations to Xunlong's Stephen.
<MoeIcenowy> tkaiser: oh
<MoeIcenowy> In fact
<tkaiser> Most product announcements were made by him in the last few weeks/months. And he said he got Mali libraries from Xunlong
<tkaiser> Don't know whether that's true since I used my H3 devices most if not every time headless ;)
<MoeIcenowy> I do think linux-sunxi may now maintain a kernel tree of a23/31/33/80/83, h3
<MoeIcenowy> (In fact, I tried to search for a working r4p0 driver for a summer holiday
<MoeIcenowy> (and then fell back to r3p2
<MoeIcenowy> (Moreover, do anyone here used llvmpipe on ARM?
<MoeIcenowy> (Some of my binaries uses libGL rather than libGLESv2
<MoeIcenowy> (they get very very slow performance on ARM devices
<MoeIcenowy> (using softpipe
<MoeIcenowy> (I built a llvmpipe mesa
<MoeIcenowy> (but found the image rendered is broken
<MoeIcenowy> (But after I choose to the llvmpipe mesa, gnome-shell got usable
<MoeIcenowy> Ohhhhh, I consider the jacer copy of mali binary driver broke the GPL
<MoeIcenowy> kernel modules and libUMP.so have no source shipped
<tkaiser> Surprised?
<MoeIcenowy> not surprised
<MoeIcenowy> but now I daren't to use it
bmeneg has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
viccuad has quit [Quit: WeeChat 1.3]
soderstrom has quit [Quit: leaving]
bmeneg has quit [Quit: WeeChat 1.3]
oliv3r has left #linux-sunxi [#linux-sunxi]
FDCX has quit [Read error: Connection reset by peer]
viccuad has joined #linux-sunxi
xenoxaos has joined #linux-sunxi
xenoxaos has quit [Client Quit]
tkaiser has quit [Quit: jIRCii - http://www.oldschoolirc.com]
xenoxaos has joined #linux-sunxi
<MoeIcenowy> I will start a project to make a generic new-generation sunxi kernel
<MoeIcenowy> (As my kernel base -- SinA33 A33 Lichee kernel is not stable enought to met my requirments
<MoeIcenowy> (ALSA cannot be used under it
<MoeIcenowy> (Both using audiocodec and connecting a USB audio stick will make it panic
vishnup has joined #linux-sunxi
<MoeIcenowy> But now I'm only collection lichees
<MoeIcenowy> collecting
bmeneg has joined #linux-sunxi
<MoeIcenowy> Is there anyone that can help me to do this work?
<mripard> MoeIcenowy: you know that it's kind of exactly how linux-sunxi started ?
<MoeIcenowy> I think so
<MoeIcenowy> But when linux-sunxi started
<MoeIcenowy> I do not even own an ARM device
<mripard> then the effort ujst need to be continued
FDCX has joined #linux-sunxi
<MoeIcenowy> (In fact nowadays linux-sunxi have so many lichees
<mripard> there's a lack of manpower, not will
<MoeIcenowy> (ye
<MoeIcenowy> (yes
<mripard> so I'm not sure you need to create your own fork
<mripard> just pick up the offerort
<MoeIcenowy> (However, to add support of sun8,9i to linux-sunxi seems to be even more difficult than create a new one
<MoeIcenowy> (As sunxi changed a lot
<mripard> yeah, but fixing all the drivers to fix the same bugs that were fixed years ago also is painful
<MoeIcenowy> ?
<jelly> you're going to want to have that shit upstream in the end, so long term it makes a lot of sense to join the project that's already doing it
<MoeIcenowy> what project?
<MoeIcenowy> mainlineize?
<jelly> linux-sunxi
<MoeIcenowy> jelly: I do not care A10, 13, 20
<MoeIcenowy> but I care new SoCs
<MoeIcenowy> they're in new wafer-based naming styles
<MoeIcenowy> Selfishly what I want is just a stable A33 tree
<mripard> and using linux-sunxi will give you an headstart doing that
<mripard> since the drivers are mostly the same
<mripard> and we've been using them for years
<MoeIcenowy> But it seems that more drivers are in new lichee
<MoeIcenowy> for example
<MoeIcenowy> esp8089
<mripard> then merge the new ones, use the stable older ones
<MoeIcenowy> OK I will consider it
<MoeIcenowy> however... how to merge the arch/arm/mach-sunxi guys?
<MoeIcenowy> I'm not familiar with this part
<jelle> hmm there is a driver for esp8089, kinda forgot if my tablet had that one
<MoeIcenowy> it seems that no esp8089 in https://github.com/linux-sunxi/linux-sunxi
<MoeIcenowy> (to be honest, the robust of the esp8089 driver shipped in lichee is a negative
<MoeIcenowy> (When I loaded the module without the firmware
<MoeIcenowy> (it panic!!!
<rellla> MoeIcenowy: your idea of a new fork is respectable, but imho a deadend and counterproductive. efforts should be spent to mainline
<MoeIcenowy> but something is said to be not able to be merged into mainline
<MoeIcenowy> for example
<MoeIcenowy> nand
<MoeIcenowy> cedar
<rellla> why not cedar?
<rellla> why not nand?
<MoeIcenowy> cedar creates a specific device node
<MoeIcenowy> nand is not the kind of thing that kernel does
<MoeIcenowy> (I said the software FTL by aw
<rellla> sure. as for cedar. it has to be rewritten. http://linux-sunxi.org/VE_Planning
<MoeIcenowy> No
<MoeIcenowy> I don't think a v4l2 device a good idea
<MoeIcenowy> maybe combine cedar and disp in a kms card is a better choice
<MoeIcenowy> It simulated a PC graphics card
cptG_ has quit [Quit: Konversation terminated!]
<MoeIcenowy> (mali can be another card, and thus it's an "optimus"
<jelle> MoeIcenowy: so the driver is in the sdk?
<MoeIcenowy> jelle: esp8089? yes in A33 SDK
<jelle> oh meh
<jelle> that's a funky androidish linux kernel right?
<MoeIcenowy> jelle: it's said be
<MoeIcenowy> however, I haven't built an Android using this kernel
domidumont has quit [Remote host closed the connection]
<MoeIcenowy> and I don't believe it's stable enought for a productive Android system
<MoeIcenowy> s/enought/enough
<jelle> neither for mainline
<MoeIcenowy> jelle: right
domidumont has joined #linux-sunxi
<MoeIcenowy> rellla: In addition, does mainline kernel now has driver for a33 disp?
<MoeIcenowy> (seems to be a generation between a10/13/20's and h3's
<rellla> MoeIcenow: mainline kernel is lacking all of the media things still. disp, ve, mali. though work is in process afaik.
<mripard> the A33 display engine is the same one as A13's
<rellla> independent of the SoC version.
<MoeIcenowy> mripard: Why do they have different userspace API?
<mripard> it changed with the A83
domidumont has quit [Remote host closed the connection]
<mripard> don't know, and don't really care.
<MoeIcenowy> mripard: I'll go to check datasheet now
<MoeIcenowy> mripard: may the wip sunxi-disp kms driver work?
<mripard> that's exactly what I'm testing since this morning
<mripard> but yeah, I expect it to work
<MoeIcenowy> mripard: you also have an a33?
<mripard> it does so in U-Boot, so it should be mostly working on linux as well
<mripard> yes
<MoeIcenowy> how to build a bootable SD for a33
<MoeIcenowy> (with mainline guys
domidumont has joined #linux-sunxi
<wens> MoeIcenowy: see Mainline U-boot on the wiki
<jelle> MoeIcenowy: I took an fedora armv7 image, slapped my own kernel + u-boot on it
<MoeIcenowy> I'll now go to buy a new SD card
<MoeIcenowy> (In fact I may find one under my table
<MoeIcenowy> (TF card is too easy to be lost
<MoeIcenowy> in addition, what can I do as my devices seems to have no UART pads
<MoeIcenowy> (my another a33 board have one, but that a33 board is now a portable router)
<wens> what boards do you have?
<MoeIcenowy> not a board
<MoeIcenowy> a tablet
<MoeIcenowy> Aoson_M751s
<jelle> MoeIcenowy: I think u-boot has otg support.. so you might be able to hookup mouse and keyboard
<MoeIcenowy> (the router is a white-brand one
<jelle> ah yeah that's how hans didi t
<jelle> but you need to load a usb gadget driver in the kernel
<MoeIcenowy> hmm
<jelle> or solder uart cables, but that means opening it up
<MoeIcenowy> I opened it
<MoeIcenowy> but found no UART pads on the pcb
<jelle> MoeIcenowy: that's how I did it http://linux-sunxi.org/File:TZX-723Qa4.JPG
<MoeIcenowy> my device is Aoson M751s
<MoeIcenowy> I've uploaded high-resolution PCB image to linus-sinxi
<MoeIcenowy> sunxi
<libv> MoeIcenowy: did you try the rear?
<MoeIcenowy> i didn't
<MoeIcenowy> ping
<MoeIcenowy> why I saw i'm leaving
MoeIcenowy has left #linux-sunxi ["AndroIRC - Android IRC Client ( http://www.androirc.com )"]
MoeIcenowy has joined #linux-sunxi
<MoeIcenowy> got a 8gb sd class 4
<MoeIcenowy> maybe not enough for rootfs
<MoeIcenowy> but enough for a kernel :-)
_stephan has quit [Quit: Ex-Chat]
SadSmile has quit [Quit: Leaving]
<MoeIcenowy> mripard: your disp can now work under uboot?
cnxsoft has quit [Quit: cnxsoft]
<vickycq> Are FEX files from stock Android image more or less 'broken'?
<mripard> MoeIcenowy: "now" ?
<vickycq> I extracted the script from the Foxconn provided Android imageusing script_extrator and compared it with Bananapi.fex
<vickycq> ...
<mripard> it's been the case for more than a year...
<vickycq> ...and I see a lot of differences. However booting Linux with extracted script worked.
<vickycq> (did not test everything.)
<libv> vickycq: :)
<vickycq> diff script_extracted Bananapi.fex: http://paste.ubuntu.com/14399706/
<MoeIcenowy> mripard: lcd?
<mripard> yes
<vickycq> ...the first thing poped up into my head is GMAC_TX_DELAY. But at the moment I don't have a Gbit router around to test
<MoeIcenowy> libv: unfortunately, nothing is on the rear pcb
<libv> MoeIcenowy: photo :)
<MoeIcenowy> libv: a huge black sticker is on it
<MoeIcenowy> (It seems to be because the screen have a steel back
<MoeIcenowy> (and I daren't open the sticker
<MoeIcenowy> If mripard's work is OK
<MoeIcenowy> may I boot a mainline kernel with lcd?
<MoeIcenowy> and input with a USB keyboard?
<MoeIcenowy> (Or except SD what other port can be broken out as a UART?
<mripard> MoeIcenowy: in u-boot, it's not my work, it's libv's and hans'
<MoeIcenowy> ok
<MoeIcenowy> a33 ehci is ok?
<MoeIcenowy> @mripard
IgorPec has quit [Ping timeout: 246 seconds]
<MoeIcenowy> libv: but in script.bin I found uart0 and uart1 is both activated
<MoeIcenowy> (This tablet have no bluetooth
mosterta has quit [Ping timeout: 240 seconds]
<MoeIcenowy> mripard, libv: Do you have any manuals on writting dtbs?
kaspter has joined #linux-sunxi
<mripard> MoeIcenowy: I've not tested EHCI for quite some time, but it should be
<MoeIcenowy> mripard: for lcd and ehci which u-boot tree do I need?
<MoeIcenowy> is git://git.denx.de/u-boot.git ok?
fl_0 has quit [Ping timeout: 260 seconds]
<mripard> yes
FlorianH has quit [Ping timeout: 264 seconds]
<MoeIcenowy> mripard: thx
<MoeIcenowy> and should I begin my device tree base on Sin-A33 dt?
fl_0 has joined #linux-sunxi
<MoeIcenowy> thus... after the talk today
<MoeIcenowy> I found that some mainline info on linux-sunxi is not up-to-date at al
<MoeIcenowy> all
<MoeIcenowy> which used to make me not hopeful to mainline
<MoeIcenowy> (but today I got my spirit back
<mripard> MoeIcenowy: which ones?
<MoeIcenowy> for example
<MoeIcenowy> To get U-Boot output shown on the built-in framebuffer driver (currently, HDMI only at 1024x768), add the following to your boot.cmd:
<MoeIcenowy> In "FB console"
<mripard> have you read literaly the first line on that page.
<mripard> ?
<MoeIcenowy> Terrible
<MoeIcenowy> I misread it
<MoeIcenowy> Sorrrrrrry
<MoeIcenowy> In addition, is there a page for U-Boot like Linux_mainlining_effort ?
<yann|work> MoeIcenowy: have an H3 here, still need any info ?
<MoeIcenowy> yann|work: no
<jelle> orange pi pc boots with upstream u-boot
<jelle> *which is h3*
<MoeIcenowy> jelle: yes? interesting
<MoeIcenowy> (It seems that use upstream uboot to boot lichee kernel is also something beneficial
<MoeIcenowy> (At least I can get rid of the script.bin embedded in uboot
JohnDoe7 has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 255 seconds]
<ssvb> MoeIcenowy: yes, you can boot lichee kernels with the upstream uboot
<MoeIcenowy> ssvb: I found these infomation
<ssvb> at least this works on a10/a13/a20 and h3
FlorianH has joined #linux-sunxi
<MoeIcenowy> ssvb: it should also work on A33
<MoeIcenowy> A33 also have script.bin at 0x43000000
Guest36876 is now known as jero-
<MoeIcenowy> I used dd from /dev/mem to acquire script.bin from there
<ssvb> if you find that some information in the wiki is not clear enough, feel free to improve it
Ueno_Otoko has quit [Ping timeout: 250 seconds]
<MoeIcenowy> mripad: is there any manuals for converting script.fex into uboot's .config and linux's dt?
<vickycq> ...I also would like to know about this
<mripard> for u-boot, yes.
<mripard> for the DT, not at the moment
<MoeIcenowy> mripard: where
<MoeIcenowy> In addition, I found SinA33_defconfig nearly null..
<MoeIcenowy> ...
FlorianH has quit [Ping timeout: 260 seconds]
<mripard> that was also linked in the first line of the page you pasted...
<MoeIcenowy> mripard: Can I safely ignore the blank options of usbc, mmc pins
<mripard> it depends on your board
<MoeIcenowy> I don't think so
<MoeIcenowy> but there's no manual to set them
avph has quit [Read error: Connection reset by peer]
<MoeIcenowy> In addition ,what's "port:power2<1><0><default><1>" in uboot?
<MoeIcenowy> power2?
<MoeIcenowy> port: power2
<MoeIcenowy> or AXP0-2?
<MoeIcenowy> and is CONFIG_VIDEO_LCD_BL_PWM pwm_positive in pwm0_para?
FlorianH has joined #linux-sunxi
<vishnup> wens: I'm trying to switch on regulators on axp81x. what extra care should i take to avoid over voltage?
<vishnup> like if on board 3.3V is there I'm keeping it to 3V only, for now.
<MoeIcenowy> After dealing with .config of uboot, I can only get such a conclusion:
<MoeIcenowy> There's now nearly no document for mainlineing
<ssvb> MoeIcenowy: well, u-boot custodians do not care much about the documentation
<vickycq> 'urban soas
<vickycq> sorry, wrong channel
<ssvb> MoeIcenowy: http://linux-sunxi.org/Mainline_U-Boot#Adding_a_new_device_to_upstream_U-Boot has a link to the Hans de Goede's e-mail, which represents his best effort in this area
<MoeIcenowy> ssvb: far from enough
<ssvb> well, because there is no shortage of people contributing defconfigs for allwinner boards to u-boot, this is probably good enough for everyone?
<MoeIcenowy> but people like me are adding support for new boards
<jelle> which board?
<ssvb> MoeIcenowy: in principle, we can have the kernel dts and u-boot defconfig automatically converted from fex
<ssvb> some of this has been already done for the u-boot LCD settings - http://linux-sunxi.org/LCD#Bulk_automatic_conversion_of_all_FEX_files_from_the_sunxi-boards_repository
<ssvb> and it could be relatively easily expanded to generate the whole u-boot defconfig and dts
<ssvb> the main idea (as you can see in the wiki page) is that the conversion script also tries to 'grade' the quality of the conversion results and highlights them with different colors
<MoeIcenowy> hmm
<ssvb> and provides annotations in comments about what is suspicious and needs to be checked by the user
<MoeIcenowy> of course these can be done in productive script by adding "FIXME"
<ssvb> but mripard did not particularly like this idea and promised not to merge any patches from the users relying on such (semi-)automatic conversion: http://lists.denx.de/pipermail/u-boot/2015-January/202312.html
<ssvb> the hardship in trying to do all of this labor manually probably rewards you with a better understanding about how the hardware actually works and improves the quality of your contribution :-)
<MoeIcenowy> I now have the feeling that can be told by a Chinese proverb
<MoeIcenowy> "The angels fights, and the people got hurt"
<wens> vishnup: not getting what you're asking
<wens> vishnup: regulator contraints in the dts are there to keep outputs from going over voltage
<vishnup> wens: I'm retrying to add axp81x. just don't want to blow up my board in experiments.
<mripard> ssvb: yeah, what could go wrong by massively converting poorly-written files to another format when those files can fry your board.
<MoeIcenowy> mripard: This is not the reason for not providing manuals and documents
<vishnup> wens: as I understand axp20x.c has constraints which will avoid over-voltage,and what we write in dts is what voltage we want for particular regulator.
<vishnup> isn't it true?
<wens> vishnup: the values in axp20x-regulator.c are the min/max values or "valid range" for the regulator
<wens> they have nothing to do with your board constaints, which you define in the dts
naobsd has joined #linux-sunxi
<wens> what you write in the dts is what the consumer can take, i.e. the recommended operating parameters
vishnup has quit [Ping timeout: 250 seconds]
viccuad has quit [Ping timeout: 245 seconds]
vishnup has joined #linux-sunxi
premoboss has quit [Quit: Sto andando via]
premoboss has joined #linux-sunxi
<ssvb> mripard: well, that's rather weak argument, considering how sloppy the default clock frequencies and voltages are handled in U-Boot
<ssvb> and you can still have to potentially deal with the guys copy-pasting stuff from other dts files without understanding what this means
vishnu_ has joined #linux-sunxi
premoboss has quit [Client Quit]
<vishnu_> wens: Thanks, that helps me understand more.
<mripard> MoeIcenowy: tag, you're it.
<ssvb> mripard: and this is open source, I just offered to do some work for free, and you promised to harass the potential users
<mripard> harass, really?
<ssvb> mripard: when we discussed dts patches the last time, you acted pretty obnoxious and demonstrated poor comprehension skills
<MoeIcenowy> mripard: ?
<mripard> I'm sorry you feel like I'm a jerk, and a dumb one
avph has joined #linux-sunxi
<MoeIcenowy> To many users and developers
<MoeIcenowy> stock scripts is the best info srv
<MoeIcenowy> src
<libv> MoeIcenowy: which is why collecting them, together with other valuable device information, is such an important point in our new device howto
<mripard> ssvb: and I stand by what I said, I won't merge a DT that has not been tested on some real hardware. I really don't see what's unreasonable about that, but feel free to educate me
<MoeIcenowy> mripard, ssvb: Above anything, proper document is still important
<MoeIcenowy> for examplr
<MoeIcenowy> example
<MoeIcenowy> you'd provide description to the options
<mripard> and I really don't see the point of supporting poorly every board out there. I'm more enclined to first support a few ones as good as we can, and then merge new boards. I know a lot of people here feel differently, so I try to get in the way as less as possible, but we actually end up these days with no device properly supported, and everyone reviewing yet-another-board, ending up in no progress whats
<mripard> oever.
<mripard> MoeIcenowy: you have that description in Documentation/devicetree/bindings already
<vishnu_> wens: I'm able to see atleast power button interrupt from axp81x :). your patches are very helpful adding support .
<wens> :)
<MoeIcenowy> mripard: I even get difficult to convert fex pin "power2" to uboot config pin
IgorPec has joined #linux-sunxi
Seppoz has quit [Ping timeout: 255 seconds]
<mripard> MoeIcenowy: it seems to be AXP0-2
<mripard> judging from the other examples
<MoeIcenowy> mripard: you don't also know?
<MoeIcenowy> zi
<MoeIcenowy> I also think it's AXP0-2
<ssvb> MoeIcenowy: you can check the allwinner kernel sources and then contribute to improving http://linux-sunxi.org/Fex_Guide#Port_Definitions
<ssvb> MoeIcenowy: and you can also compare fex files for some boards with u-boot defconfigs for the same boards
<ssvb> MoeIcenowy: you have an advantage over all of us: you are new here :-) so you can actually spot problems in the documentation, while it is more difficult for the other people who are already familiar with this stuff
<MoeIcenowy> :-)
<MoeIcenowy> I may do this tomorrow
<MoeIcenowy> as my dorm's power supply is broken
KotCzarny has quit [Ping timeout: 272 seconds]
domidumont has quit [Read error: Connection reset by peer]
nove has joined #linux-sunxi
Seppoz has joined #linux-sunxi
arossdotme has joined #linux-sunxi
<nove> MoeIcenowy: samsung, freescale, mediatek, qualcom and rockchip, have in mainline kernel or are doing a V4L2 mem2mem driver for respective (VPU, Video Codec) hardware (what ever is called)
vagrantc has joined #linux-sunxi
<nove> MoeIcenowy: i don't see any reason why, sunxi should be any different
<vagrantc> ssvb: thanks for the link to your branch for the H3 support ... unfortunately, ehci-platform wouldn't build so i had to disable the reset-control and ehci patch ... which effectively disabled USB i think
<vagrantc> no ethernet yet, either :(
<vagrantc> i wonder if the ehci patches just break when compiling as a module, but might work as a built-in ... if i can get USB to work on it, i can at least use a USB ethernet adapter
<ssvb> vagrantc: how does it break?
<ssvb> vagrantc,
<ssvb> I'm pretty sure that it compiled fine for me
<ssvb> vagrantc: can you try an unmodified sunxi_defconfig?
<ssvb> vagrantc: btw, https://github.com/ssvb/linux-sunxi/commit/cfc97602a935fa5dd5c84ab3da5bc61cc3426ce9 change is there exactly for using it with USB ethernet adapter
<ssvb> probably your board has a built-in USB hub and needs some special dts magic
<ssvb> for example, Orange Pi Plus initializes USB in the following way - https://github.com/ssvb/linux-sunxi/commit/f31f74a2c3070ba35e9eea03f7afda86d3e715ee
Andy-D has quit [Remote host closed the connection]
KotCzarny has joined #linux-sunxi
mawe242 has quit [Ping timeout: 260 seconds]
yann|work has quit [Ping timeout: 276 seconds]
pmattern has joined #linux-sunxi
<vagrantc> ssvb: it fails to build ... i can dig up the build log
premoboss has joined #linux-sunxi
<vagrantc> ssvb: ERROR: "of_reset_control_get_by_index" [drivers/usb/host/ehci-platform.ko] undefined!
<vagrantc> ssvb: disabling two of the patches from your tree allowed it to build.
khuey|away is now known as khuey
<vagrantc> full build log at: https://www.aikidev.net/~vagrant/h3/
<ssvb> vagrantc: have you tried to compile it as built-in?
<vagrantc> not yet, that was my next plan
<vagrantc> i could also just try dropping in the sunxi_defconfig
* ssvb uses this kernel to boot over NFS, so compiling USB support as modules (or anything else critical for networking) makes little sense
<ssvb> maybe you have found a bug, or maybe there was a more recent revision of this patch
<vagrantc> yeah, your patch is simply weeks old! :)
<vagrantc> or, branch
<ssvb> it's not my patch, that's the stuff scavenged from the mailing lists :)
<ssvb> I don't know how these patches are routed into the mainline kernel and from which tree they are going to be merged, so let's just wait for the first 4.5 release candidate
vishnu_ has quit [Ping timeout: 260 seconds]
vishnup has quit [Ping timeout: 260 seconds]
<vagrantc> for the short-term, if building the modules in works for me, that's fine.
<vagrantc> ssvb: but your branch got me pretty far along, so thanks! :)
FlorianH has quit [Ping timeout: 255 seconds]
apritzel has quit [Ping timeout: 246 seconds]
_massi has quit [Remote host closed the connection]
reinforce has joined #linux-sunxi
Netlynx has joined #linux-sunxi
Netlynx has joined #linux-sunxi
FlorianH has joined #linux-sunxi
FlorianH has quit [Ping timeout: 260 seconds]
viccuad has joined #linux-sunxi
Andy-D has joined #linux-sunxi
domidumont has joined #linux-sunxi
IgorPec2 has joined #linux-sunxi
IgorPec has quit [Ping timeout: 246 seconds]
IgorPec2 has quit [Ping timeout: 246 seconds]
gzamboni has quit [Read error: No route to host]
mawe242 has joined #linux-sunxi
<vagrantc> well, including usb support as a built-in at least compiles
* vagrantc tests if it works
Netlynx has quit [Quit: Leaving]
gzamboni has joined #linux-sunxi
viccuad has quit [Read error: Connection reset by peer]
bonbons has joined #linux-sunxi
<ssvb> vagrantc: and?
<vagrantc> ssvb: might be working as a built-in
* vagrantc rummages around for devices to plug in
<vagrantc> yup, recognizes usb ethernet
<ssvb> great!
<vagrantc> dunno if the usb ethernet works, but it sees it
<vagrantc> so, apparently, there's something with the reset/ehci patches that break compiling as modules
JohnDoe7 has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
<vagrantc> i presume the ERROR: "of_reset_control_get_by_index" [drivers/usb/host/ehci-platform.ko] undefined! ... indicates that of_reset_control_get_by_index isn't available to modules
* vagrantc tries an SSD plugged into the sata port
<ssvb> vagrantc: it looks like just one module wants to access a symbol from another which is not getting exported properly
<vagrantc> i guess the sata port is actually just a built-in usb device
<ssvb> that's a reportedly a rather slow USB-to-SATA-bridge, unless Orange Pi Plus2 got a better one
viccuad has joined #linux-sunxi
domidumont has quit [Ping timeout: 246 seconds]
pietrushnic has quit [Ping timeout: 264 seconds]
<jelle> you really need a powered usb hub for these boards right?
pietrushnic has joined #linux-sunxi
yann|work has joined #linux-sunxi
<vagrantc> gah. ever since i plugged in the sata device, it only boots from flash, not u-boot on my microSD
<vagrantc> even after unplugging the sata
<vagrantc> ok, writing a few zeros to the eMMC(?) seems to have fixed it
* vagrantc wonders if the built-in usb sata is slow enough that using an external USB-SATA device wouldn't be faster
<KotCzarny> do a test?
<vagrantc> of course
<vagrantc> it seems "dd if=/dev/zero of=/dev/sda1 bs=10240k count=10" does 14.7MB/s
<vagrantc> and "sudo dd if=/dev/sda1 of=/dev/null bs=10240k count=10" does 32.1MB/s
<KotCzarny> um, do: time (dd ...something.. ; sync)
<KotCzarny> otherwise you wont count the mem buffered blocks
<vagrantc> i thought sync only affected filesystems, not raw block devices
<KotCzarny> afair doing sync after dd returns still writes quite a bit of data
<KotCzarny> and as long you dont do o_direct, you still go through the cache
bpi-user has joined #linux-sunxi
<vagrantc> the sync manpage suggests it only affects filesystems
<vagrantc> results are virtually identical ... only minr fractions of a MB/s different
<KotCzarny> oh.
jinzo has quit [Quit: Leaving]
<vagrantc> i suspect dd to a file from a mounted filesystem would be very different, of course... or maybe the sync manpage isn't correct
* vagrantc shrugs
<vagrantc> i'm just looking for ballpark figures anyways
<KotCzarny> ahm, right
<vagrantc> is it definitely way faster/slower
bpi-user has quit [Quit: Page closed]
<vagrantc> well, i think i have a kernel that's usable enough for now, eagerly awaiting H3 support getting merged into 4.5 :)
<vagrantc> would be nice to figure out the USB module issue
<jelle> linux hdegoede's branch also works nice on my orange pi pc
<vagrantc> ssvb's branch was a small enough set that i could apply it onto debian's kernel build.
* vagrantc eyes up the cubieboard4 for another round of wrangling
ricardocrudo has quit [Ping timeout: 265 seconds]
mawe242 has quit [Ping timeout: 240 seconds]
Ntemis has joined #linux-sunxi
bonbons has quit [Quit: Leaving]
mawe242 has joined #linux-sunxi
<mawe242> mripard, quick question about the A10/A20 SPI patch series I've been working on: when I update the series and include the clock control fixes (which you said should be CCed to -stable), do I send the whole series to all recipients, or each patch separately to the recipients relevant for only the single patch?
IgorPec has joined #linux-sunxi
yann|work has quit [Ping timeout: 260 seconds]
<mawe242> or as it's a rather generic question about kernel development, maybe someone else here can help me?
destroyedlolo has joined #linux-sunxi
<destroyedlolo> Hello
<destroyedlolo> Can someone give me the usage of "autotp" section of fex file ?
<destroyedlolo> I didn't find anything on the Internet :(
<KotCzarny> what device it is?
<KotCzarny> also, have you tried bin2fex'ing random fexes?
IgorPec2 has joined #linux-sunxi
<destroyedlolo> It's for my HC-913 tablet (https://linux-sunxi.org/MID-KLIPAD_HC-913) and yes, i found them when converting its Android bin.
IgorPec has quit [Ping timeout: 246 seconds]
IgorPec2 has quit [Ping timeout: 246 seconds]
premoboss has quit [Remote host closed the connection]
<vagrantc> hrm.
<vagrantc> now it fails to boot, no serial console output, nothing
<vagrantc> just when i thought i was making progress
<vagrantc> power mnitor at 5.01 v, 0.05 amp
nove has quit [Quit: nove]
<vagrantc> sd card seems fried
<ssvb> try to disconnect all the potential sources of power (barrel plug, usb otg, uart) before trying to boot it again
<vagrantc> nothing
<ssvb> is the sd card still readable in a pc card reader?
<vagrantc> in a usb reader, yes. in a microSD to SD adapter, no.
<ssvb> it could be also a grease/dust problem
* vagrantc suspects a new power supply did some evil, or electrostatic discharge from moving it
<vagrantc> and now it's working with the SD adapter again
* vagrantc shrugs
<vagrantc> i've got a second one to try...
<ssvb> try to wipe the sd card connector pads, they could be a bit greasy
<ssvb> if you accidentally left your fingerprints on it
<vagrantc> behaves the same with several different microSD cards
<vagrantc> well, that doesn't look good. second board seems to work.
robogoat has quit [Ping timeout: 240 seconds]
mawe242 has quit [Quit: Leaving]
<vagrantc> hrm. but usb ethernet doesn't work...
* vagrantc wonders about firmware
<vagrantc> the usb-sata bridge seems to work, the usb/microsd adapter works ...
robogoat has joined #linux-sunxi
* vagrantc really hopes that other board isn't bricked
destroyedlolo has quit [Quit: Leaving]
naobsd has quit [Remote host closed the connection]
<vagrantc> usb ethernet does appear to work... something made the rootfs ro, so didn't change my networking changes.
<vagrantc> didn't save...
<vagrantc> FWIW, the internal usb-sata bridge on the orangepi-plus2 performs almost identically to an external usb-sata bridge i've got
<vagrantc> though still about 50-75% the speed of the same external device plugged into another board
Ntemis has quit [Read error: Connection reset by peer]