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
<apritzel> catphish: so you rely on u-boot setting the PHY up for you?
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
<apritzel> I wonder if it wouldn't be easier to code everything as a new u-boot cmd ...
akaizen has quit [Remote host closed the connection]
FDCX has quit [Ping timeout: 265 seconds]
<catphish> i'll look into init'ing it fully
catphish has quit [Quit: Leaving]
FDCX has joined #linux-sunxi
interrobangd has quit [Quit: Leaving]
Ueno_Otoko has joined #linux-sunxi
khuey is now known as khuey|away
apritzel has quit [Ping timeout: 246 seconds]
hipboi has joined #linux-sunxi
IgorPec has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
viccuad has quit [Ping timeout: 260 seconds]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
IgorPec has quit [Quit: Nettalk6 - www.ntalk.de]
ricardocrudo has quit [Ping timeout: 250 seconds]
ninolein has quit [Ping timeout: 240 seconds]
ninolein has joined #linux-sunxi
hipboi has quit [Quit: This computer has gone to sleep]
akaizen has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 255 seconds]
naobsd has joined #linux-sunxi
TheSeven has quit [Ping timeout: 260 seconds]
TheSeven has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 260 seconds]
TheLinuxBug has quit [Ping timeout: 260 seconds]
akaizen has quit [Remote host closed the connection]
TheLinuxBug has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 250 seconds]
p1u3sch1 has joined #linux-sunxi
akaizen has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
hipboi has joined #linux-sunxi
IgorPec has joined #linux-sunxi
vishnup has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
dadada has joined #linux-sunxi
dadada is now known as Guest1326
Ueno_Otoko has quit [Ping timeout: 260 seconds]
clonak has quit [Ping timeout: 272 seconds]
IgorPec2 has joined #linux-sunxi
IgorPec has quit [Ping timeout: 246 seconds]
IgorPec2 has quit [Ping timeout: 246 seconds]
clonak has joined #linux-sunxi
alexxy has quit [Ping timeout: 240 seconds]
alexxy[home] has joined #linux-sunxi
mawe242 has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
bmeneg has quit [Ping timeout: 264 seconds]
bmeneg has joined #linux-sunxi
domidumont has joined #linux-sunxi
IgorPec has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
premoboss has quit [Remote host closed the connection]
yann|work has quit [Ping timeout: 265 seconds]
clonak has quit [Ping timeout: 272 seconds]
clonak has joined #linux-sunxi
indy has quit [Ping timeout: 260 seconds]
rgwan has joined #linux-sunxi
focus has joined #linux-sunxi
premoboss has joined #linux-sunxi
indy has joined #linux-sunxi
caog has joined #linux-sunxi
_massi has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
yann|work has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
enrico_ has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 240 seconds]
premoboss has quit [Ping timeout: 255 seconds]
caog has quit [Ping timeout: 260 seconds]
apritzel has joined #linux-sunxi
premoboss has joined #linux-sunxi
reinforce has joined #linux-sunxi
viccuad has joined #linux-sunxi
iamfrankenstein1 has quit [Quit: iamfrankenstein1]
lemonzest has joined #linux-sunxi
hp197 has joined #linux-sunxi
naobsd has quit [Quit: naobsd]
rgwan has quit [Ping timeout: 260 seconds]
Gerwin_J has quit [Ping timeout: 246 seconds]
mpmc has quit [Ping timeout: 256 seconds]
mpmc has joined #linux-sunxi
catphish has joined #linux-sunxi
rgwan has joined #linux-sunxi
leio has joined #linux-sunxi
leio has quit [Remote host closed the connection]
leio has joined #linux-sunxi
Worf has joined #linux-sunxi
pmattern has joined #linux-sunxi
HeHoPMaJIeH has quit [Quit: Konversation terminated!]
Ueno_Otoko has joined #linux-sunxi
premoboss has quit [Ping timeout: 272 seconds]
premoboss has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
premoboss has quit [Ping timeout: 255 seconds]
vishnu_ has joined #linux-sunxi
premoboss has joined #linux-sunxi
viccuad has quit [Ping timeout: 276 seconds]
caog has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
viccuad has joined #linux-sunxi
hipboi has quit [Quit: This computer has gone to sleep]
Worf has quit [Quit: Konversation terminated!]
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
premoboss has quit [Quit: Sto andando via]
MaDMaLKaway has quit [Remote host closed the connection]
iamfrankenstein1 has quit [Ping timeout: 245 seconds]
iamfrankenstein has quit [Ping timeout: 276 seconds]
iamfrankenstein has joined #linux-sunxi
Guest-en has quit [Remote host closed the connection]
<apritzel> hi, does it sound useful if I write some ARM64 intro somewhere into the Wiki?
<apritzel> mostly comparing and contrasting it to ARM(32)?
<libv> apritzel: we are not wikipedia
<libv> feel free to link to wikipedia pages though
<apritzel> libv: that's why I was thinking of a more technical description, focusing on people knowledgeable of 32-bit ARM and pointing out differences
<libv> apritzel: how relevant is that to support A64 SoCs and to get software running on them?
<libv> and to what extent is this not rehashing information that is available somewhere else?
<apritzel> to understand what Allwinner did wrong in their firmware ;-)
<apritzel> and how to fix it ...
<libv> then start off by explaining what allwinner did wrong, not with explaining armv8
<libv> i and others spent ages getting structure into and removing cruft from our wiki, and most of that cruft was either copies of wikipedia or translations
viccuad has quit [Ping timeout: 260 seconds]
<libv> apritzel: that sounds like it belongs on the A64 soc page
<apritzel> kind of
<mripard> apritzel: more context would still be valuable, like why it's actually wrong, how it's supposed to behave, etc
<apritzel> not sure if the firmware provided isn't specific to the Pine64
<libv> and it in itself is a pretty apt explanation
<libv> apritzel: i really really doubt that the pine64 guys are doing anything much themselves
<apritzel> me too, but Allwinner may provide them with something specific to their board
<apritzel> like the DRAM parameters are surely DRAM chip specific, aren't they?
viccuad has joined #linux-sunxi
<libv> yes, but switching to armv8 when starting u-boot, or switching to it much much later, is not a trivial difference like the setup of the dram controller
<libv> this is not going to be board specific
<apritzel> possibly, I guess I will move it to the SoC page then
<apritzel> actually to me switching to AArch64 sound much easier than setting up a DRAM controller ;-)
<libv> i do really like that explanation though, and imho it does not need more explanation at all
<libv> apritzel: perhaps, but perhaps they were scared of what they might run into with uboot, or perhaps (allwinners version of) uboot needs work
<apritzel> libv: Allwinner's u-boot is complete shite ;-)
<libv> dram controller setup is always board specific
<libv> whether it is more complicated than switching to aarch64 or not
tkaiser has joined #linux-sunxi
<apritzel> I was hoping to hack their u-boot to allow an upstream kernel to boot (in EL2), but now I will hack the kernel instead for a quick start
<libv> well, setup isn't, the configuration parameters are.
<tkaiser> apritzel: Have you had a look into http://www.murlock.org/a64/lichee_A64_A5.1_V1.0.tar.gz
<tkaiser> This one leaked before the pine guys put their variant of the BSP on google drive mid December
<libv> tkaiser: we should perhaps collect those on linux-sunxi.org so that those things do not drop off the interweb
<apritzel> tkaiser: interesting, I only have the one referenced by the Pine64 guys
<apritzel> but if the other one is even older, I don't expect anything good from it ;-)
<libv> and i am amazed that someone asked on that cnx thread whether there was a community for a64 :)
<tkaiser> But IIRC I was able u-boot back then with this BSP variant
<tkaiser> That contains nothing Pine64 specific
<libv> soc specific communities are soo 2012 :)
<apritzel> tkaiser: actually it doesn't need to, if DRAM setup has happened before
<apritzel> the rest can probably be rather board agnostic (apart from a DT, maybe)
vishnup has quit [Quit: Connection closed for inactivity]
viccuad has quit [Ping timeout: 256 seconds]
<apritzel> and they have a huge DT in their u-boot (have to find out where that comes from, but it prints with "fdt print")
<apritzel> of course mostly totally incompatible with any kind of mainline bindings
<apritzel> not to speak of the totally made-up and random additional bindings
<apritzel> the only good things is that it's a good source of Soc/board specific parameters
<apritzel> for instance it has a list of DRAM parameters
<libv> so they moved away from fex with a64?
* libv has not been paying that much attention these past few months
<apritzel> libv: looks like it to me
<tkaiser> Nope, still there
<libv> so now we have both?
<apritzel> tkaiser: in the BSP code?
<apritzel> I found it being optional there (can be configured out)
<tkaiser> Both and maybe even conflicting :)
<libv> pffff
<tkaiser> Ok
<libv> then we need to start collecting both as well :(
<tkaiser> I played with this stuff in the mid of Dec and forgot almost everything in the meantime
viccuad has joined #linux-sunxi
<tkaiser> apritzel: sys_config.fex being optional would make sense. They can provide their customers with what they're used to and get new customers to start over with DT instead
<apritzel> tkaiser: would make sense
<libv> but it does require that we collect both when available
<libv> *sigh*
<apritzel> I found their idea of structuring the firmware actually being quite OK
<mripard> apritzel: and the "made-up and additional bindings" is mostly fex "properties" they dumped into the DT
<mripard> so they didn't really moved away from it, it's just some frankentree
<apritzel> for instance moving the PMIC control into the firmware and using a generic driver communicating with the RISC core
Deskwizard has quit [Ping timeout: 265 seconds]
Ueno_Otoko has quit [Ping timeout: 250 seconds]
pmattern has quit [Ping timeout: 260 seconds]
pmattern_ has joined #linux-sunxi
<wens> apritzel: that is actually very old, starting with A31
<wens> we just weren't using it
<apritzel> wens: ah, OK, but it sounds useful to me
<apritzel> IMHO the kernel shouldn't really be bothered with setting up voltages and stuff
<apritzel> sounds dangerous to me
<mripard> it depends
<mripard> sometimes you just don't have the choice :)
<apritzel> mripard: I see that when it comes to the quality of their existing firmware code, yes ...
<mripard> there's that
<mripard> but I was mostly talking about the voltage that can change
<mripard> for example, you might have a voltage changing when using an MMC
<mripard> at runtime
<mripard> and then, you have to have at least some control over your regulators
<apritzel> sure, but that again could be done by signalling the ARISC, which does some range checking on the requested voltage and prevents you from accidentally frying your card/board/chip ...
mnr has joined #linux-sunxi
<mripard> I wonder if we could write our own firmware based on rpmsg
<apritzel> mripard: sounds good to me (having just briefly browsed over Documentation/rpmsg.txt)
afaerber has joined #linux-sunxi
<mripard> I have a basic driver that loads a firmware to the ar100 and starts executing it
<mripard> I was planning on porting it to remoteproc
hipboi has joined #linux-sunxi
viccuad has quit [Ping timeout: 276 seconds]
pmattern has joined #linux-sunxi
pmattern_ has quit [Ping timeout: 260 seconds]
<vishnu_> mripard: h3 clock gates driver doesn't seem to be user friendly
<vishnu_> what would be ideal approach for gates clock?
<vishnu_> simple-gates or the h3 way?
<mripard> "user friendly" ?
<mripard> what do you mean?
<vishnu_> I mean, in person who write dts has to count 0-128 like that
<vishnu_> instead of referring to reference manual and use same bit number in dtsi
<mripard> simple-gates works the same way
<mripard> and you are referring to the reference manual
<mripard> the number in the is register * 32 + bit
Andy-D has quit [Ping timeout: 250 seconds]
hipboi has quit [Quit: This computer has gone to sleep]
hipboi has joined #linux-sunxi
<vishnu_> yes, but in case of sun8i-h3.dtsi, gates clock indices ranges from 0-135.
viccuad has joined #linux-sunxi
<mripard> well, yeah, there's more, but there's more register to control the gates as well
<mripard> the thing is we have to model the clocks per "block"
<mripard> the bus gates stuff is a single bloc
<mripard> so we don't really have much choice anyway
Andy-D has joined #linux-sunxi
<vishnu_> for A83T, do you mind if we go ahead with separate node for each 32-bit gates register ?
<mripard> please don't do that
<mripard> this is a single hardware block that is spread across several registers, it should be a single DT node and a single driver
<vishnu_> mripard: okie, thanks. I'll do it similar to h3.
<mripard> if you don't have multiple parents to the bus gates, you can just use simple-gates
caog has quit [Quit: Ex-Chat]
hipboi has quit [Quit: This computer has gone to sleep]
orly_owl has quit [Ping timeout: 260 seconds]
vishnup has joined #linux-sunxi
<ssvb> mripard: very cool, I was also going to start on ar100 driver for the linux kernel but if you can take care of it, then it is the best
iamfrankenstein has quit [Quit: iamfrankenstein]
<ssvb> mripard: the biggest question is whether we can allow it to load and run untrusted code in linux
iamfrankenstein has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 265 seconds]
<ssvb> mripard: I'm looking forward to checking a solution that you come up with
domidumont has quit [Write error: Connection reset by peer]
tomboy64 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 264 seconds]
rgwan has quit [Remote host closed the connection]
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 240 seconds]
yann|work has quit [Ping timeout: 246 seconds]
JohnDoe_71Rus has joined #linux-sunxi
MaDMaLKaV has joined #linux-sunxi
soderstrom has joined #linux-sunxi
soderstrom has quit [Ping timeout: 246 seconds]
domidumont has joined #linux-sunxi
matthias_bgg has quit [Quit: Leaving]
mawe242 has quit [Quit: Leaving]
catphish has quit [Quit: Leaving]
apritzel1 has joined #linux-sunxi
Netlynx has joined #linux-sunxi
khuey|away is now known as khuey
<apritzel> mmh, is the SID register accessible from secure state only?
FDCX has quit [Ping timeout: 255 seconds]
tomboy65 has quit [Ping timeout: 250 seconds]
tomboy65 has joined #linux-sunxi
lemonzest has quit [Quit: Leaving]
tomboy65 has quit [Ping timeout: 245 seconds]
FDCX has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
viccuad_ has joined #linux-sunxi
viccuad has quit [Ping timeout: 255 seconds]
viccuad_ has quit [Client Quit]
apritzel1 has quit [Ping timeout: 246 seconds]
FDCX has quit [Ping timeout: 276 seconds]
vishnu_ has quit [Quit: Leaving]
apritzel has quit [Ping timeout: 246 seconds]
soderstrom has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
yann|work has joined #linux-sunxi
enrico_ has quit [Quit: Bye]
tomboy64 has quit [Ping timeout: 260 seconds]
FDCX has joined #linux-sunxi
_massi has quit [Remote host closed the connection]
vishnup has quit [Quit: Connection closed for inactivity]
tomboy65 has quit [Ping timeout: 272 seconds]
tkaiser has quit [Ping timeout: 260 seconds]
tomboy66 has joined #linux-sunxi
FDCX has quit [Ping timeout: 276 seconds]
tomboy66 has quit [Ping timeout: 240 seconds]
tomboy64 has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 260 seconds]
tomboy65 has quit [Ping timeout: 240 seconds]
FDCX has joined #linux-sunxi
akaizen has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
Deskwizard has joined #linux-sunxi
apritzel has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 240 seconds]
akaizen has quit [Remote host closed the connection]
Turl has quit [Remote host closed the connection]
Turl has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
tkaiser has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 250 seconds]
tomboy64 has joined #linux-sunxi
akaizen has joined #linux-sunxi
arossdotme has joined #linux-sunxi
arossdotme-planb has quit [Ping timeout: 255 seconds]
tomboy64 has quit [Ping timeout: 255 seconds]
arossdotme has quit [Quit: Ex-Chat]
arossdotme has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
apritzel1 has joined #linux-sunxi
FDCX has quit [Remote host closed the connection]
afaerber has quit [Quit: Ex-Chat]
tomboy64 has quit [Ping timeout: 246 seconds]
tomboy64 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 265 seconds]
iamfrankenstein1 has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
iamfrankenstein1 has quit [Quit: iamfrankenstein1]
tomboy64 has quit [Ping timeout: 265 seconds]
ricardocrudo has quit [Remote host closed the connection]
Netlynx has quit [Quit: Leaving]
domidumont has quit [Read error: No route to host]
p1u3sch1 has quit [Ping timeout: 264 seconds]
p1u3sch1_ has joined #linux-sunxi
domidumont has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
arossdotme-planb has joined #linux-sunxi
arossdotme has quit [Ping timeout: 245 seconds]
domidumont has quit [Ping timeout: 246 seconds]
mnr has quit [Quit: leaving]
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 265 seconds]
IgorPec2 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 265 seconds]
IgorPec has quit [Ping timeout: 246 seconds]
arossdotme has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Equilibrium 4.2.0, revision: 42021, sources date: 20120701, built on: 2013-10-21 12:25:22 UTC 42021 http://www.kvirc.net/]
IgorPec2 has quit [Ping timeout: 246 seconds]
arossdotme-planb has quit [Ping timeout: 256 seconds]
Guest1326 has quit [*.net *.split]
diego71_ is now known as diego71
interrobangd has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
tomboy65 has quit [Ping timeout: 255 seconds]
tomboy65 has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 255 seconds]
iamfrankenstein has quit [Quit: iamfrankenstein]
iamfrankenstein1 is now known as iamfrankenstein
tomboy65 has quit [Ping timeout: 265 seconds]
tomboy65 has joined #linux-sunxi
FDCX has joined #linux-sunxi
khuey is now known as khuey|away
tomboy65 has quit [Ping timeout: 276 seconds]
FDCX has quit [Remote host closed the connection]
FDCX has joined #linux-sunxi
khuey|away is now known as khuey
FDCX has quit [Remote host closed the connection]
FDCX has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
yann|work has quit [Ping timeout: 260 seconds]
SMD1 has joined #linux-sunxi
<SMD1> Hi everyone!
<SMD1> I'm wondering if there are some owners of OPi Pc: have you succeeded to run eth and usb hosts in uboot?
arossdotme-planb has joined #linux-sunxi
arossdotme has quit [Ping timeout: 276 seconds]
tomboy65 has quit [Read error: Connection reset by peer]
arossdotme has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
arossdotme-planb has quit [Ping timeout: 250 seconds]
tomboy65 has quit [Ping timeout: 272 seconds]
ricardocrudo has joined #linux-sunxi
<ssvb> SMD1: uboot does not support this yet
<SMD1> ssvb: Thanks. Do you know if anyone works on this now? I'd like to help but I think I need some assistance and advice.
arossdotme-planb has joined #linux-sunxi
FDCX has quit [Ping timeout: 264 seconds]
arossdotme has quit [Ping timeout: 240 seconds]
\\Mr_C\\ has joined #linux-sunxi
tomboy64 has joined #linux-sunxi
<ssvb> SMD1: there are patches for USB host support on Allwinner H3 for the Linux kernel
<ssvb> you can try to have a look at them and port to U-Boot
reinforce has quit [Quit: Leaving.]
<ssvb> Ethernet is still not supported on H3, but montjoie is working on a driver for the Linux kernel
FDCX has joined #linux-sunxi
arossdotme has joined #linux-sunxi
arossdotme-planb has quit [Ping timeout: 260 seconds]