Turl changed the topic of #linux-sunxi to: All systems go! // 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
khuey_ is now known as khuey|away
gianMOD has joined #linux-sunxi
el3 has quit [Remote host closed the connection]
gianMOD_ has joined #linux-sunxi
leviathancn has quit [Ping timeout: 245 seconds]
gianMOD has quit [Ping timeout: 250 seconds]
gianMOD_ has quit [Ping timeout: 250 seconds]
mmarker has joined #linux-sunxi
wenbin has joined #linux-sunxi
<Turl> quitte: include/linux/interrupt.h
<ssvb> libv: appears that sunxi-tools is packaged in some distributions (or at least being considered to be packaged)
<ssvb> libv: in this case, imho having a generic 'meminfo' name for a tool is not a very good idea
Andy-D has joined #linux-sunxi
<ssvb> libv: should it be probably renamed to something like 'sunxi-meminfo'?
<quitte> Turl: http://linux-sunxi.org/NFC_Register_Guide#NFC_ST is close to what I hoped for. Doesn't look very trustworthy, however
guizamboni has quit [Quit: Leaving]
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
gianMOD has joined #linux-sunxi
gianMOD has quit [Ping timeout: 256 seconds]
Renard has quit [Quit: Renard]
khuey|away is now known as khuey_
cnxsoft has joined #linux-sunxi
akaizen has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
akaizen has quit [Ping timeout: 245 seconds]
akaizen_ has joined #linux-sunxi
popolon has quit [Quit: WeeChat 1.1.1]
akaizen has joined #linux-sunxi
akaizen_ has quit [Read error: Connection reset by peer]
AnticitizenOne has joined #linux-sunxi
gianMOD has joined #linux-sunxi
gianMOD has quit [Ping timeout: 252 seconds]
<ijc> ssvb: debian-installer> Yes, one of them. The other is mostly karsten merkler (spelling?) who has been producing the sdcard images. I'm mostly involved on the kernel+initrd.gz side of it.
<ssvb> ijc: is there a plan to upgrade the kernel to something that supports simplefb?
mmarker has quit [Read error: Connection reset by peer]
<ijc> ssvb: Not for Debian 8 (Jessie), it's been frozen for months. If the backports are reasonably self contained then we could probably justify that. A list of commits in a Debian bugreport would be the best way to achieve that.
<ijc> I'm at a conference and having a meeting in 3mins, so going AFK now
mmarker has joined #linux-sunxi
<ssvb> ijc: ok, thanks
disdi has joined #linux-sunxi
disdi has quit [Client Quit]
gianMOD has joined #linux-sunxi
gianMOD has quit [Ping timeout: 246 seconds]
FergusL has quit [Read error: Connection reset by peer]
FergusL has joined #linux-sunxi
AnticitizenOne has quit [Ping timeout: 252 seconds]
Novtopro has joined #linux-sunxi
Novtopro has quit [Client Quit]
Novtopro has joined #linux-sunxi
Novtopro has quit [Client Quit]
p1u3sch1 has joined #linux-sunxi
khuey_ is now known as khuey|away
p1u3sch1_ has quit [Ping timeout: 245 seconds]
TheSeven has quit [Ping timeout: 265 seconds]
TheSeven has joined #linux-sunxi
RaYmAn has quit [Ping timeout: 245 seconds]
RaYmAn has joined #linux-sunxi
RaYmAn is now known as Guest65508
gianMOD has joined #linux-sunxi
gianMOD has quit [Ping timeout: 255 seconds]
Andy-D has quit [Ping timeout: 256 seconds]
orly_owl has joined #linux-sunxi
Andy-D has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
gianMOD has joined #linux-sunxi
gianMOD has quit [Ping timeout: 264 seconds]
ssvb has quit [Ping timeout: 246 seconds]
reinforce has joined #linux-sunxi
nemunaire has quit [Ping timeout: 252 seconds]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
gianMOD has joined #linux-sunxi
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
igorpec has joined #linux-sunxi
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
quitte_ has joined #linux-sunxi
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
quitte has quit [Ping timeout: 265 seconds]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
wenbin has quit [Ping timeout: 264 seconds]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
wenbin has joined #linux-sunxi
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
gianMOD has quit [Remote host closed the connection]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
wenbin has quit [Read error: Connection reset by peer]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
igorpec has quit []
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
nemunaire has quit [Excess Flood]
nemunaire has joined #linux-sunxi
HeHoPMaJIeH has joined #linux-sunxi
ninolein has quit [Ping timeout: 246 seconds]
ninolein has joined #linux-sunxi
wenbin has joined #linux-sunxi
gianMOD has joined #linux-sunxi
gianMOD has quit [Ping timeout: 245 seconds]
reinforce has quit [Quit: Leaving.]
reinforce has joined #linux-sunxi
wenbin has quit [Read error: Connection reset by peer]
wenbin has joined #linux-sunxi
_massi has joined #linux-sunxi
a1d3s|away is now known as a1d3s
cubear has joined #linux-sunxi
sehraf has joined #linux-sunxi
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
arete74 has quit [Ping timeout: 246 seconds]
<oliv3r> goooooood morning all
<wens> morning
gianMOD has joined #linux-sunxi
<rellla> morning
<quitte_> morning
<quitte_> http://linux-sunxi.org/NFC_Register_Guide#NFC_ST is this informatin available with more detail in a manual?
<bbrezillon> quitte_: how could it work in the first place, if you're not even able to read the NAND status now ?
<quitte_> bbrezillon: I don't know. It does the nand detection fine. I double checked by removing the chip definition
<bbrezillon> quitte_: have you enabled the NAND controller clock ?
<bbrezillon> okay, if the detection works, then the READ_STATUS should work
<quitte_> bbrezillon: yes. i had printfs and the clock was switched to 10Mhz and to some higher value
<quitte_> bbrezillon: maybe it's the way read_status is called let me find the function...
<bbrezillon> quitte_: is there a timeout ?
<quitte_> bbrezillon: there are no timeouts happening in wait_in or the fifo clear
<bbrezillon> could you show me your code ?
<quitte_> you mean the code that fails? it's not exactly mine. just a second.
Guest65508 is now known as RaYmAn
arete74 has joined #linux-sunxi
a1d3s is now known as a1d3s|away
<quitte_> all the following checks get 0x70,too
<bbrezillon> quitte_: where is cmd_ctrl assigned ?
<quitte_> ugh. I don't know. I'm fairly sure it is the sunxi_nand implementation because it gets executed.
<bbrezillon> could you add traces in the sunxi_nfc_wait_int func ?
<bbrezillon> and check if it timeouts
<quitte_> I wouldn't knwo where to start. Do I need to connect jtag?
<quitte_> it does not timeout. printf in the timeout case was not executed
<quitte_> otoh this might be worth redoing. this i don't know from a clean situation
<quitte_> bbrezillon: nfc->regs + NFC_RAM0_BASE is this cleared when the contents are latched by the NFC?
<bbrezillon> quitte_: just add some traces (printf) in the sunxi_nfc_wait_int to check if it times out
<quitte_> if that is what you consider a trace okay will do it. It did not timeout. I'l still recheck with no other modifications...
<bbrezillon> quitte_: how could you know it didn't timeout ? Nobody's checking the return code of this func...
<quitte_> bbrezillon: i added that printf
<bbrezillon> quitte_: sorry, oversight your answer
<quitte_> it's rebuilding right now so there'll be a definite answer in a few minutes
<quitte_> no timeout
<bbrezillon> quitte_: could you add traces in sunxi_nfc_cmd_ctrl displaying the dat and ctrl values
<bbrezillon> and add a trace in nand_check_wp (before and after the cmdfunc call), so that we can see which arguments are passed to cmd_ctrl
<fest> I'm still trying to read camera sensor data from CSI interface, and I don't understand memory addressation in linux kernel. I am passing dma_addr_t which I got from dma_alloc_coherent to CSI, and then trying to read something at vaddr (return value from dma_alloc_coherent_call). Is there something else I should do with regards to DMA (e.g. set up source and target addresses etc), or is the problem with
<fest> sensor init/clocks/IOs?
<fest> (CSI capture_done IRQ fires though, so I suppose that pclk/hsync works)
popolon has joined #linux-sunxi
naobsd has quit [Quit: naobsd]
naobsd has joined #linux-sunxi
<bbrezillon> quitte_: you miss a writel on the NFC_REG_ST register
gianMOD has quit [Remote host closed the connection]
FR^2 has joined #linux-sunxi
gianMOD has joined #linux-sunxi
gianMOD has quit [Remote host closed the connection]
gianMOD has joined #linux-sunxi
<bbrezillon> quitte_: try with this => http://code.bulix.org/fex2zb-87863
gianMOD has quit [Remote host closed the connection]
<mripard_> fest: I'd say it depends on wether you're doing peripheral DMA or using an external DMA controller
gianMOD has joined #linux-sunxi
gianMOD has quit [Remote host closed the connection]
wickwire has joined #linux-sunxi
gianMOD has joined #linux-sunxi
el3 has joined #linux-sunxi
quitte_ has quit [Read error: Connection reset by peer]
<fest> mripard_: I'm using sun4i, but programmers manual doesn't go into too much detail
gianMOD has quit [Ping timeout: 264 seconds]
<mripard_> fest: but yeah, most likely you will need to setup the buffers address that the device will fill
di-erz has joined #linux-sunxi
<mripard_> the way you're doing it will differ though
<mripard_> either you'll have to use the Allwinner DMA API
<mripard_> or you'll have to poke some registers in the CSI itself
quitte has joined #linux-sunxi
<fest> yeah, already do pass dma_addr to CSI
<fest> I also don't see any special dma api calls in existing drivers
<quitte> bbrezillon: I'm not sure about what traces you want for the WP check. the nand_ctrl arguments are hard coded
<quitte> ...cmd_ctrl
<quitte> cmdfunc
gianMOD has joined #linux-sunxi
<quitte> is what i should have said, only
<bbrezillon> quitte: those traces are fine actually
<bbrezillon> quitte: have you tried reworking the sunxi_nfc_wait_int func as I suggested ?
<quitte> yes. the pastebin already has it
<quitte> I even tried clearing the interrupt flags on success myself, yesterday
_massi has quit [Quit: Leaving]
_massi has joined #linux-sunxi
<quitte> but I really don't understand this self modifying flag check
<bbrezillon> we don't care about interrupts here, cause we're not using the
<quitte> yes. but you are checking for its flags
<quitte> aren't you?
<bbrezillon> I'm checking for the status
Andy-D has quit [Ping timeout: 252 seconds]
<bbrezillon> could you print the NFC_REG_ST value in the cmd_ctrl func, before writing on NFC_REG_CMD
<mripard_> fest: so it's probably using peripheral DMA hten
<fest> mripard_: so in theory I only need to pass it physical address, and after IRQ, data from sensor should be written to that address, right?
<mripard_> well, I'm not sure about the "only" here, but yeah, something like that
<mripard_> the devil's in the details
<bbrezillon> quitte: by clearing interrupt flags you mean in NFC_REG_INT, right ?
<quitte> no in NFC_REG_ST
<quitte> bbrezillon: are those registers documented in something allwinner provided?
<bbrezillon> nope
<quitte> all the more impressive of a job you did
<bbrezillon> hm, actually I'm not the one who did the reverse enginering work
<bbrezillon> I just use those information to develop the driver
<quitte> similar to the NFC register page in the wiki? still impressive
ricardocrudo has joined #linux-sunxi
hipboi has joined #linux-sunxi
<bbrezillon> quitte: so, what's the value of NFC_REG_ST before this test => http://code.bulix.org/109ola-87864
<quitte> sorry had to fix typo. still building
hipboi_ has quit [Ping timeout: 245 seconds]
<quitte> sunxi_nfc_cmd_ctrl NFC CMD REG before: 0x400038
<bbrezillon> okay, sounds good
<bbrezillon> quitte: could you add a loop reading several byte in the nand_check_wp func ?
<bbrezillon> (start with a 100 time)
<bbrezillon> then test the last value
<quitte> bbrezillon: nand unlock does not use that. I could loop in nand_unlock?
<quitte> the nand_unlock is nice because it does very little
<bbrezillon> nope, I really want it to be done after the NAND_CMD_STATUS cmd is sent
<bbrezillon> quitte: what's your NAND chip again ?
marcin has quit [Read error: Connection reset by peer]
<quitte> hynix
wenbin has quit [Read error: Connection reset by peer]
<bbrezillon> can you try to lower the NAND clk ?
<quitte> 0.5?
<bbrezillon> 20MHz
marcin has joined #linux-sunxi
<quitte> ugh
<quitte> i guess i could find it somehow
<bbrezillon> quitte: it works ?
<quitte> #define NAND_MAX_CLOCK (10 * 1000000)
<quitte> the clock should already be limited to 10 MHZ?
<quitte> no it does not work
<quitte> bbrezillon: if you are referring to the nand chip - it works in linux, yes.
<bbrezillon> quitte: no, I was referring what you're currently testing :-)
<quitte> i'm not testing anything. i now added a trace to tell what hz value set_clk_rate is passed
<bbrezillon> quitte: can you try the multiple read_byte thing ?
<quitte> setting clock to 100000000 Hz
<quitte> that is a 0 more than 10 Mhz
<quitte> oh that
<quitte> i think i added that. but it didn't happen....
<quitte> sigh goto. of course it does not loop
<quitte> bbrezillon: do you want me to reread without sending the NAND_GET_STATUS?
<bbrezillon> yep
<quitte> then it'll take another while
<bbrezillon> quitte: just to be sure, which reg value did you print before writing in the NFC_CMD_REG register ?
<quitte> this 100Mhz thing is weird.
<bbrezillon> just keep 10MHz
<quitte> i did not change it but the trace reports 100
<bbrezillon> it is reconfigured after the NAND chip has been detected
<bbrezillon> please, let's focus on the status register for now
<bbrezillon> could you paste a diff so that I can check you're printing the appropriate value ?
<quitte> tmp = readl(nfc->regs + NFC_REG_CMD);
<quitte> okay. I'll paste as is
<bbrezillon> quitte: that's not what I asked
<quitte> oops. sorry
<bbrezillon> I want NFC_REG_ST's value
<quitte> yes. changed it. sorry
ricardocrudo has quit [Ping timeout: 264 seconds]
<quitte> the loop did not help
<quitte> NAND: setting clock to 10000000 Hz
<quitte> setting clock to 28571428 Hz
<quitte> i'm bad at counting 0s
<quitte> setting clock to 100000000 Hz
<quitte> there it is
<quitte> this happens late. I'll enforce 10Mhz once I have NFC_REG_ST
forest has quit [Quit: Leaving]
<quitte> 0xf01
gianMOD has quit [Remote host closed the connection]
wickwire has quit [Ping timeout: 252 seconds]
wickwire has joined #linux-sunxi
<bbrezillon> quitte: try to add that to your nand_unlock code => http://lxr.free-electrons.com/source/drivers/mtd/nand/nand_base.c#L985
<quitte> the reset?
Andy-D has joined #linux-sunxi
<bbrezillon> yep
<quitte> no change
Renard has joined #linux-sunxi
<quitte> bbrezillon: it's not only that bit 7 is not set, but the other set bits are always 0 in a status response, according to the hynix datasheet
<quitte> also just ignoring the WP status doesn't help much
<bbrezillon> quitte: then I don't know, I' guess you'll have to figure it out on your
di-erz has quit [Read error: Connection reset by peer]
di-erz has joined #linux-sunxi
<quitte> bbrezillon: thanks for your help. again about the ram0 - shouldn't this be empty?
<quitte> bbrezillon: it seems to me that the 0x70 in there doesn't even get latched into the NFC
<quitte> so later it's still there and read back
ssvb has joined #linux-sunxi
Administrator_ has joined #linux-sunxi
<Administrator_> hello
Administrator_ has quit [Client Quit]
f15h has joined #linux-sunxi
Steven__ has joined #linux-sunxi
Steven__ has quit [Client Quit]
Steven__ has joined #linux-sunxi
Steven__ has quit [Client Quit]
Steven__ has joined #linux-sunxi
<Steven__> hello everyone
gianMOD has joined #linux-sunxi
<Steven__> How to exchange data between A20 and FPGA or other CPU with high speed?
cubear has quit [Quit: Leaving]
<quitte> Steven__: what is "high"?
<Steven__> To exchange data through bus or DMA channel, is it possbile?
<quitte> of course it is. SPI is not exactly slow. But PCIe is probably the most sensible choice
<fest> mripard_: it seems that I haven't configured the sensor correctly- if I write to the dma address before sensor __should__ be doing that, that memory is overwritten by zeroes
<mripard_> yeah, so it looks like the CSI is doing its dma accesses, but the data it sends are bad
gianMOD has quit [Read error: Connection reset by peer]
<mripard_> so it's probably something else than DMA that is wrong
<mripard_> quitte: there's no PCIe on the Allwinner SoCs.
<quitte> mripard_: true. but Steven did not specify allwinner. i.MX6 has PCIe
<mripard_> well, he did mention the A20.
<quitte> on the allwinners sdio is probably the best fast bus for fpga
<mripard_> I remember someone mentionning putting an FPGA on the DRAM bus on the ML some time ago
<mripard_> I'm not sure how far he went with that
<quitte> i'm aware of the concept. but that blocks ram access
<quitte> it's part of what ruined the gta02
<quitte> openmoko
<mripard_> well, yeah, of course
<Steven__> This is a disadvange for using A20.
<quitte> sdio is not that bad. the question is wether it is fast enough
<quitte> however if spi is fast enough - it's damn easy to implement
<Steven__> Ok, I see. Ths very much.
F1skr has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
ssvb has quit [Ping timeout: 252 seconds]
aep has quit [Ping timeout: 244 seconds]
aep has joined #linux-sunxi
Black_Horseman has quit [Ping timeout: 255 seconds]
afaerber has joined #linux-sunxi
el3 has quit [Quit: Leaving]
iamfrankenstein has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
iamfrankenstein has joined #linux-sunxi
sdschulze has joined #linux-sunxi
Steven__ has quit [Ping timeout: 245 seconds]
<sdschulze> I'm using an A20 (OLinuXino LIME2 board) with mainline Linux 3.16, but there is no HDMI signal during boot-up. Maybe the HDMI code hasn't been mainlined yet?
<mripard_> sdschulze: the HDMI code hasn't been mainlined
<mripard_> but we have some restricted HDMI support with the help of the bootloader since 3.19
<mripard_> and with u-boot 2015.01
<sdschulze> Ah, ok. So I need X11 to get output?
<mripard_> X11 or anything that can work on top of a framebuffer
FR^2 has quit [Quit: Connection reset by peer]
<sdschulze> But I need a forked kernel for framebuffer, too, right?
<sdschulze> I don't really *need* HDMI console output for boot-up, I was just wondering if I was doing something wrong.
imcsk8 has quit [Quit: Reconnecting]
imcsk8 has joined #linux-sunxi
<mripard_> sdschulze: no, you don't, as long as its a 3.19 kernel with u-boot 2015.01.
<sdschulze> Ok, thanks. I will try that once it gets into Debian. :)
<oliv3r> mripard_: your mainline spi driver, is that full-duplex atm?
<T0mW> Is the LVDS console working with simple framebuffer in 3.19? I've got a console with u-boot 2015.01, but yet to get 3.19 booting. Just wondering if my LVDS display would be borking the 3.19?
<T0mW> So far, I've an LVDS console with u-boot 2015.01 and the linux-sunxi 3.4.102 working
afaerber has quit [Quit: Verlassend]
afaerber has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
tomcheng76 has quit [Read error: Connection reset by peer]
a1d3s|away is now known as a1d3s
focus has quit [Ping timeout: 245 seconds]
tomcheng76 has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
<mripard_> oliv3r: I think it was
<mripard_> why?
<mripard_> T0mW: you might need some more recent kernels and u-boot for lvds
<T0mW> mripard_: the 3.4.102 is working okay, the 3.19 not booting yet.
<T0mW> mripard_: no simple framebuffer node being passed into 3.4.102, I understand that, but at least u-boot is visible with 2015.01.
<T0mW> my concern is to get 3.19 working so I have any bugfixes since the 3.4.102 release
<mripard_> what do you mean by "not booting yet" ?
<T0mW> heh, no output on serial console.
<T0mW> plays dead
<mripard_> on which board? with which defconfig?
<T0mW> the linux-next-3.19 booted, obviously no framebuffer in that
<T0mW> it is an A20 board
selfbg has joined #linux-sunxi
<T0mW> not a cubie or something like that
<mripard_> what?
<mripard_> I thought 3.19 wasn't booting?
<T0mW> Well, the pre-release git was booting, but they changed the dts stuff in the actual linus kernel.
<mripard_> define "pre-release" and "they"
selfbg has quit [Client Quit]
<T0mW> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
<T0mW> That boots, but no framebuffer
focus has joined #linux-sunxi
<mripard_> what tag are you using?
<T0mW> just master
<mripard_> master from when then
<mripard_> that tree is rebased every day
<T0mW> ah
<T0mW> ok
<fest> mripard_: haha, I just noticed that original camera drivers return a green image now (YUV values 000), so I must have damaged the sensor's outputs or A10 inputs somehow
<T0mW> didn't think about that, I should delve more deepling into using that tree then and see if I can get the simple framebuffer working in it or backport into it.
<T0mW> mripard_: thanks, I've been a bit overwhelmed with a driver deadlock.
focus has quit [Ping timeout: 264 seconds]
<mripard_> T0mW: both 3.19 and that tree should work fine
<mripard_> at least a recent linux-next
<T0mW> ok, looking at it now. Thinking to spend some time today messing with it.
<mripard_> make sure you have simplefb enabled in your configuration, and something to display in Linux
<mripard_> a good test would be to enable the framebuffer console
<T0mW> yeah, I won't pull until I figure why simple fb was not working on that source, at least it boots to a serial console.
<a1d3s> mripard is there a reason bcause of missing bananapro.dts in 3.19?
<mripard_> yeah, it was merged for 3.20
<a1d3s> will 3.20 become long term?
<mripard_> we won't know before 3.20 is out
<mripard_> but it's unlikely
<mripard_> the next one will probably be 3.22
<a1d3s> thanks :) good to know
reinforce has quit [Quit: Leaving.]
FlibberTGibbet has joined #linux-sunxi
focus has joined #linux-sunxi
viccuad has joined #linux-sunxi
orly_owl has quit [Quit: leaving]
f15h has quit [Remote host closed the connection]
focus has quit [Ping timeout: 265 seconds]
ssvb has joined #linux-sunxi
pirea has joined #linux-sunxi
pirea is now known as pirea_
pirea_ is now known as pirea
pirea has quit [Client Quit]
paulk-collins has joined #linux-sunxi
aballier has quit [Quit: leaving]
cnxsoft has quit [Quit: cnxsoft]
iamfrankenstein has joined #linux-sunxi
aballier has joined #linux-sunxi
viccuad has quit [Quit: WeeChat 1.0.1]
ricardocrudo has quit [Ping timeout: 245 seconds]
reinforce has joined #linux-sunxi
AnticitizenOne has joined #linux-sunxi
FR^2 has joined #linux-sunxi
el3 has joined #linux-sunxi
el3 has quit [Ping timeout: 252 seconds]
guizamboni has joined #linux-sunxi
kz1_ has joined #linux-sunxi
focus has joined #linux-sunxi
kz1 has quit [Ping timeout: 256 seconds]
kz1_ is now known as kz1
fredy has quit [Ping timeout: 276 seconds]
focus has quit [Ping timeout: 265 seconds]
fredy has joined #linux-sunxi
viccuad has joined #linux-sunxi
fredy has quit [Ping timeout: 240 seconds]
el3 has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
fredy has joined #linux-sunxi
<sdschulze> Now I'm using sunxi-linux 3.4, but my monitor still says "no signal" on the HDMI input. I set "console=tty0" in the bootargs. Anything else?
<plaes> which u-boot?
<sdschulze> u-boot-sunxi
<sdschulze> recent git checkout
<sdschulze> syslog even claims: "Console: switching to colour frame buffer device 160x45"
domidumont has joined #linux-sunxi
<sdschulze> Adding "disp.screen0_output_mode=EDID" doesn't do anything, either.
<sdschulze> Should I try mainline u-boot?
<quitte> sdschulze: yes
<sdschulze> Ok, I'll try that.
<sdschulze> The other problem was that my network connection doesn't get started, but I'm blaiming systemd for that right now. ;)
HeHoPMaJIeH has quit [Quit: Konversation terminated!]
tobrebski_ has quit [Quit: Leaving]
<sdschulze> Mainline u-boot works. :)
nove has joined #linux-sunxi
FlibberTGibbet has quit [Quit: Leaving]
<sdschulze> ... except that it's not booting the kernel any more...
nuuhku has joined #linux-sunxi
vishnup has joined #linux-sunxi
AnticitizenOne has quit [Ping timeout: 240 seconds]
bonbons has joined #linux-sunxi
afaerber_ has joined #linux-sunxi
afaerber has quit [Ping timeout: 246 seconds]
AnticitizenOne has joined #linux-sunxi
vishnup has quit [Quit: Leaving]
_massi has quit [Quit: Leaving]
vishnup has joined #linux-sunxi
domidumont has quit [Ping timeout: 246 seconds]
domidumont has joined #linux-sunxi
<nuuhku> Finally got kernel 3.19 working with a Cubieboard 2 and an usb sound card. Emilio's v4 dma patch works great... this is so cool!
<nuuhku> Is there an updated A20 on-chip codec patch available somewhere? The only one I can find is from last July.
forest has joined #linux-sunxi
Froolap has joined #linux-sunxi
f15h has joined #linux-sunxi
TheOnlyJoey has left #linux-sunxi ["Leaving"]
p1u3sch1 has quit [Ping timeout: 255 seconds]
ricardocrudo has quit [Ping timeout: 244 seconds]
domidumont has quit [Ping timeout: 246 seconds]
bengal has joined #linux-sunxi
p1u3sch1 has joined #linux-sunxi
khuey|away is now known as khuey_
vishnup has quit [Quit: Leaving]
mmarker has quit [Ping timeout: 264 seconds]
sehraf has quit [Quit: www.miranda-fusion.de ... be part of it...]
bonbons has quit [Quit: Leaving]
wickwire has quit [Read error: Connection reset by peer]
guizamboni has quit [Ping timeout: 245 seconds]
guizamboni has joined #linux-sunxi
Seppoz has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
vishnup has joined #linux-sunxi
Steven__ has joined #linux-sunxi
Steven__ has quit [Ping timeout: 245 seconds]
xeros has joined #linux-sunxi
libcg has joined #linux-sunxi
<Turl> nuuhku: what are you using dma for? :)
<Turl> nuuhku: the codec patches should be mostly ok, I'll see about pushing a rebased codec branch together with dma v5
Zboonet has joined #linux-sunxi
AnticitizenOne has quit [Ping timeout: 244 seconds]
<nuuhku> Turl, err... probably nothing. :) I just assumed even usb audio needed the new dma stuff.
<Turl> :p
f15h has quit [Remote host closed the connection]
libcg has quit [Quit: libcg]
<nuuhku> But now I have the perfect reason for getting the codec working on latest mainline. Oh yes... dma will be used today. 8)
bonbons has joined #linux-sunxi
ricardocrudo_ has joined #linux-sunxi
ricardocrudo has quit [Ping timeout: 240 seconds]
ricardocrudo_ has quit [Ping timeout: 250 seconds]
FR^2 has quit [Quit: Connection reset by peer]
bengal has quit [Ping timeout: 245 seconds]
khuey_ is now known as khuey|away
paulk-collins_ has joined #linux-sunxi
b0f00n has joined #linux-sunxi
paulk-collins has quit [Ping timeout: 255 seconds]
<b0f00n> Hi ! 1. How to enable keyboard at boot process ? 2. How to change the display resolution to 1920x1200@60Hz ? Where are all possible display modes/resolutions written ?
<b0f00n> this is my problem : The current input timing is not supported by the monitor display. Please change your input timing to 1920x1200@60Hz or any monitor listed timing as per the monitor specification.
<b0f00n> this happens when I try to load the kernel after boot I get this display notice
paulk-collins_ has quit [Quit: Quitte]
paulk-collins has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
<ssvb> b0f00n: what is your hardware? and what kind of software are you trying to run on it?
bonbons has quit [Quit: Leaving]
p1u3sch1 has quit [Ping timeout: 252 seconds]
<b0f00n> ssvb: hardware is pcduino3 , software is Archlinuxarm
<ssvb> WarheadsSE: ^
gianMOD has joined #linux-sunxi
<nuuhku> Ok, I think I got all relevant patches from the sunxi-codec-v0 branch applied, but alsa is not happy with sunxi-codec. No sound cards found.
<ssvb> b0f00n: if you are using the sunxi-3.4 kernel, then you can try to read some instructions at http://linux-sunxi.org/Display#HDMI
focus has joined #linux-sunxi
Andy-D has quit [Ping timeout: 250 seconds]
<sdschulze> HDMI console output works with sunxi-3.4?
<Turl> nuuhku: did you apply the dt patches?
<b0f00n> ssvb: I was playing with script.bin, setting the values for screen0_output_type = 3 and screen0_output_mode = 4 But do you maybe know if this are all the available modes to choose from, can you please look at this page, http://linux-sunxi.org/Fex_Guide#disp_init_configuration
<ssvb> b0f00n: the link I have provided to you does not touch script.bin, but adds a kernel cmdline parameter
<b0f00n> 19 disp init configuration 19.1 [disp_init]
<ssvb> b0f00n: afaik, script.bin does not support 1920x1200 screen resolution
focus has quit [Ping timeout: 255 seconds]
simosx has joined #linux-sunxi
simosx has joined #linux-sunxi
<b0f00n> ssvb: I am trying to use this yes, I mean the boot.scr file can be generated with mkimage ... what I want to say is I need to write a boot.cmd file with setenv command fro display and than generate new boot.scr can you confirm this ?
<ssvb> b0f00n: yes
<ssvb> ijc: please ping me when you have some time to chat regarding the debian installer
<nuuhku> Turl: Yes, apart from the one that disables uart dma (commit be35c0e). Seems like it was already applied or reverted. Also the duplicated stream widgets hack patch did not apply.
Black_Horseman has joined #linux-sunxi
nove has quit [Quit: nove]
<sdschulze> What u-boot do I need to get HDMI console output for the A20 with sunxi-linux-3.4? With mainline 2015.01, I see the u-boot output on screen but it freezes upon "Starting kernel...". With sunxi-u-boot trunk, it boots the kernel correctly, but there is no HDMI output at all.
<Turl> nuuhku: make sure your device's dts as well as the corresponding dtsi have the codec nodes
<ssvb> sdschulze: there is some mainline u-boot config magic, which is necessary to make it work
<ssvb> sdschulze: unfortunately, the mainline u-boot is poorly documented in the linux-sunxi wiki
<ssvb> sdschulze: feel free to check http://lists.denx.de/pipermail/u-boot/2014-December/199351.html and improve the wiki :)
<sdschulze> ssvb: But I do need mainline?
<ssvb> sdschulze: the choice is up to you
<sdschulze> (assuming I want HDMI console output)
<ssvb> sdschulze: if you need the u-boot HDMI console (for example, for the boot menu), then the mainline u-boot is the only option
<sdschulze> ok
<nuuhku> Turl: Thanks for your help. I'm double-checking the dt files right now.
<ssvb> sdschulze: and if you want HDMI output in the sunxi-3.4 kernel, then you need correct kernel configuration and this has nothing to do with u-boot
Renard has quit [Ping timeout: 264 seconds]
<ssvb> sdschulze: afaik, the sunxi-3.4 kernel supports HDMI out of the box if you use defconfigs
<ssvb> sdschulze: what is exactly your problem? u-boot console on hdmi? or linux console on hdmi?
<sdschulze> Linux
khuey|away is now known as khuey_
<sdschulze> Well the original problem is that networking doesn't get started for some reason.
<ssvb> sdschulze: what is your device?
<sdschulze> A20-OLinuXino-LIME2
<sdschulze> The latter might be a systemd issue, so my next attempt would be replacing it with sysvinit.
<sdschulze> Maybe that's easier than getting HDMI output running.
<ssvb> sdschulze: are you using the instructions from http://linux-sunxi.org/Olimex_A20-OLinuXino-Lime2 ?
<sdschulze> Yes, I've tried both mainline (from Debian) and custom-built sunxi-linux.
<ssvb> do you maybe have a dmesg log?
<sdschulze> Yes. For which one?
<sdschulze> With forked u-boot, they both boot, but neither has HDMI output.
<ssvb> the dmesg log from whatever configuration that you want to fix
<ssvb> this stuff should just normally work out of the box
<ssvb> unless you made some effort to tweak something
Renard has joined #linux-sunxi
<sdschulze> ok, just a minute...
<sdschulze> This is sunxi-linux with sunxi-u-boot now.
<ssvb> sdschulze: is your monitor maybe something like 1680x1050 by chance?
<sdschulze> ssvb: It is.
<ssvb> ok, you have "Kernel command line: console=tty0 root=/dev/mmcblk0p1 rootwait panic=10"
<sdschulze> yes
<ssvb> just add something like "hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:1280x720p60" to the kernel cmdline
<ssvb> "hdmi.audio=EDID:0" is particularly important
<sdschulze> Oh, I didn't realize the latter.
<ssvb> because the 1680x1050 monitors tend to be confused by the audio signal on the HDMI and fail to work
<ssvb> the usage is explained in http://linux-sunxi.org/Display#HDMI
<ssvb> but maybe not good enough, now I'm going to tweak the wiki
<nuuhku> Turl: Got it working! Codec routing node was missing on sun7i-a20-cubieboard2.dts file. Now I have shairport running and Miles Davis on the stereo. :)
<nuuhku> Nice work on dma and the sunxi-codec. Hope your work gets mainlined soon.
paulk-collins has quit [Quit: Quitte]
<sdschulze> ssvb: I use an HDMI-DVI adapter. Maybe that's the problem?
<sdschulze> new syslog: http://pastebin.com/W8xRVHtv
<sdschulze> No difference on the monitor, though.
konradoo77 has joined #linux-sunxi
<Turl> nuuhku: nice :)
<Turl> nuuhku: so you didn't need the hack, did you?
<ssvb> sdschulze: are you sure that there is nothing on the monitor now?
<ssvb> sdschulze: maybe try "cat /dev/urandom > /dev/fb0"
<ssvb> sdschulze: because the log looks reasonable now
<sdschulze> I can try again.
gianMOD has quit [Remote host closed the connection]
gianMOD has joined #linux-sunxi
<nuuhku> Turl: Nope, audio is working fine without it. Although, I'm not exactly sure what the hack does... is there a simple way to see if it's needed?
<ssvb> sdschulze: the HDMI-DVI adapter should not be a problem, and the hardware should be fine because the mainline u-boot can use your monitor
<ssvb> sdschulze: just try to double check everything, the missing "hdmi.audio=EDID:0" was the most likely culprit
<sdschulze> But the log says it's on the command line.
<ssvb> was the monitor powered on when you booted your board? are you sure that your system is capable of showing the login prompt on screen?
<ssvb> was there any effect from running "cat /dev/urandom > /dev/fb0"?
<sdschulze> I don't have an interactive console.
<sdschulze> Currently trying to switch to sysvinit, to exclude a systemd problem.
<sdschulze> (with my networking)
<ssvb> debugging without the uart serial console is tough
<sdschulze> I now realize I should have bought that... Though it probably involves some soldering with this board.
<ssvb> nope
<ssvb> just connecting some jumper wires, something like http://linux-sunxi.org/File:Cubieboard.UART-TTL_wire_colors.jpg
<sdschulze> Oh, I see, they have it at Olimex, too.
bsdfox has quit [Ping timeout: 246 seconds]
<sdschulze> If I had known it was that easy, I would definitely have bought that. Unbricking my Dockstar did involve some soldering, and I don't have my station here.
ssvb has quit [Ping timeout: 264 seconds]
naobsd has quit [Remote host closed the connection]
bsdfox has joined #linux-sunxi
gianMOD has quit [Remote host closed the connection]
ssvb has joined #linux-sunxi
bsdfox has quit [Ping timeout: 246 seconds]
konradoo77 has quit [Ping timeout: 255 seconds]
b0f00n has quit [Ping timeout: 246 seconds]
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-sunxi
bsdfox has joined #linux-sunxi
bsdfox has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
akaizen has quit [Ping timeout: 245 seconds]
<sdschulze> ssvb: It works with mainline u-boot.
bsdfox has quit [Ping timeout: 246 seconds]
<Turl> nuuhku: well, there was an issue that caused two widgets with the same name to be generated, and that broke it
bsdfox has joined #linux-sunxi
arossdotme has quit [Ping timeout: 246 seconds]
focus has joined #linux-sunxi
<sdschulze> Now this is strange. linux-sunxi-3.4 doesn't recognize my board's NIC.
focus_it has joined #linux-sunxi
<ssvb> sdschulze: are you using a correct script.bin for it?
focus_well has joined #linux-sunxi
<sdschulze> The one from the sunxi-boards repo.
focus has quit [Ping timeout: 250 seconds]
focus_it has quit [Ping timeout: 244 seconds]
<sdschulze> On the mainline kernel, I misconfigured it as a LIME rather than a LIME2, and it recognizes it.
<sdschulze> Maybe if I misconfigure it here, too?
iamfrankenstein has joined #linux-sunxi
<ssvb> sdschulze: the one for lime2?
focus_well has quit [Ping timeout: 265 seconds]
<sdschulze> It's actually a LIME2.
<sdschulze> Misconfiguring "pseudo-works".
<sdschulze> It keeps complaining "tx timed out".
arossdotme has joined #linux-sunxi
<sdschulze> The lime-script.bin configures it as an emac, the lime2-script.bin configures it as a gmac. The latter doesn't get recognized.
<Turl> sdschulze: did you enable the gmac driver on the kernel?
<Turl> and load it if not built as =y?
<sdschulze> It's =m.
<Turl> modprobe it then