naobsd has quit [Remote host closed the connection]
naobsd has joined #linux-sunxi
TheSeven has joined #linux-sunxi
khuey|away is now known as khuey
arete74 has joined #linux-sunxi
naobsd has quit [Remote host closed the connection]
Guest75292 has joined #linux-sunxi
naobsd has joined #linux-sunxi
Guest75292 has quit [Quit: Leaving]
TheSeven has quit [Ping timeout: 248 seconds]
cnxsoft has joined #linux-sunxi
TheSeven has joined #linux-sunxi
naobsd has quit [Remote host closed the connection]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
arokux_ has joined #linux-sunxi
arokux has quit [Ping timeout: 268 seconds]
ninolein_ has quit [Ping timeout: 250 seconds]
ninolein has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
Nyuutwo has quit [Ping timeout: 250 seconds]
mzki has quit [Quit: leaving]
apritzel has joined #linux-sunxi
Nyuutwo has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
vagrantc has quit [Quit: leaving]
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
_whitelogger_ has joined #linux-sunxi
IgorPec has joined #linux-sunxi
_whitelogger has quit [Remote host closed the connection]
FDCX has joined #linux-sunxi
Shirasaka-Hazumi has joined #linux-sunxi
reev has quit [Ping timeout: 244 seconds]
Gerwin_J has joined #linux-sunxi
reev has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
reinforce has joined #linux-sunxi
<bwarff>
im trying to port some code from pcduino kernel to armbian one which does not have the same /sys/../gpio/ structure for configuring the pins.
<bwarff>
ive got the basic in/out on/off working for my led's and power drivers
<bwarff>
but having a complete brain failure on how to get the uarts configured for ttl serial - ive copied the enabling code for the script.fex and the kernel seems to ahve picked them up
<bwarff>
however no data rx/tx on the pins...the only clue i had was the old method is to echo "3" to the mode structure and the new one doesnt have an equivilant
montjoie has quit [Quit: leaving]
arokux_ has quit [Ping timeout: 260 seconds]
yann|work has quit [Ping timeout: 248 seconds]
montjoie has joined #linux-sunxi
apritzel has joined #linux-sunxi
premoboss has quit [Ping timeout: 240 seconds]
domidumont has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
mossroy has joined #linux-sunxi
tomboy64 has quit [Ping timeout: 276 seconds]
tomboy64 has joined #linux-sunxi
focus has quit [Remote host closed the connection]
<keesj>
plaes I am using mainline for the a10 lime (olimex)
<keesj>
overall it wored quite well e.g. it was the first time ever for me that I was able to clone torvads's treen and so a simple make to get something workin on an embedded system
<plaes>
keesj: you were following wrong page
<keesj>
but DT remains very confusing. I did manage to get SPIDEV working but still not as indended (I am getting warning that my DT should be flat
<plaes>
there's a big fat warning in the header of the page :S
<keesj>
I have quite a nice little project where I added a small LCD screen (nokia 3310) to the lime enclosure and a few buttons
<plaes>
ah.. you're trying to use fbtft screen?
<plaes>
err.. fbtft driver
<keesj>
no the screen is only 84x48 pixels I am currently accessing the code from userspace
<plaes>
oh ok
<keesj>
but .. /dev/fb0 might be a nicer solution
<keesj>
I general I would like it to display the ip address of the box and perhaps a few other things
<plaes>
yeah.. then I cannot help you ;)
<plaes>
but currently SPI driver for sun4i only allows max 64byte transfers
<keesj>
Wizzup mentioned this but I already tested the display and it works
cnxsoft has quit [Read error: Connection reset by peer]
<keesj>
is it something to do with DMA?
<plaes>
ok.. then you got lucky :)
<plaes>
yes and no :)
<plaes>
DMA patches fix this issue, but there was also another patch that fixed the non-DMA case
<keesj>
the project started as a production tool to flash android devices but now I also done the PCB/display button stuff and will laser cut the cases
<keesj>
dc-gpios = <&pio 1 3 GPIO_ACTIVE_HIGH>; being the 3310 "data command" extention to SPI?
<keesj>
plaes: thanks a lot I will have a look
<keesj>
I used the same pins as olimex's uext connector (but added on extra for the backlight)
<keesj>
I need to go (flying)
<zuikis>
so, if i want to use spi I have to add it to the devicetree?
<zuikis>
i have pcduino3b (a20) and after modifying devicetree i got /sys/class/spi_master/spi0 but i was wondering if there is a way to use spi functions in kernel module without modifying devicetree
ordex has joined #linux-sunxi
<ordex>
hello
<ordex>
I have a orange pi mini (A20) and I am trying to install openwrt on my sd card, however when i try to boot it i get Could not determine boot source
<ordex>
what might be wrong ?
<zuikis>
you card may be not bootable?
<ordex>
uhm, but uboot is on the card as well - therefore it means the card is somehow booting
<ordex>
otherwise i would not see the uboot messages
<zuikis>
hmm.. i guess.. how did you create the card?
<zuikis>
plaes: interesting fact: i get /dev/spidevx created only after i register my own device with spi_new_device. However i can't do that without devicetree modification, because spi_busnum_to_master would not find master
<plaes>
hmm.. IIRC I saw something similar when I was playing with fbtft
<ordex>
plaes: yeah, quite a lot :D
<zuikis>
plaes: did you make it work in the end? Because i still have to figure out why there is no signal on the pins when i use spi, but GPIO works fine
<zuikis>
i was thinking about pinmux having to do with it, however documentations says it should work automagically
<plaes>
zuikis: I didn't use spidev
<plaes>
instead I had fbtft device
pekka30 has quit [Quit: Leaving.]
IgorPec5 has joined #linux-sunxi
IgorPec5 has quit [Client Quit]
p1u3sch1 has quit [Ping timeout: 260 seconds]
p1u3sch1 has joined #linux-sunxi
_massi has quit [Quit: Leaving]
enrico_ has quit [Quit: Bye]
IgorPec5 has joined #linux-sunxi
IgorPec5 has quit [Client Quit]
ganbold has quit [Remote host closed the connection]
Keziolio has quit [Remote host closed the connection]
khuey is now known as khuey|away
avph has joined #linux-sunxi
avph has quit [Ping timeout: 246 seconds]
nove has quit [Quit: nove]
avph has joined #linux-sunxi
bpi-user has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 244 seconds]
p1u3sch1 has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
avph has quit [Ping timeout: 246 seconds]
arokux_ has quit [Ping timeout: 250 seconds]
cosm has quit [Remote host closed the connection]
avph has joined #linux-sunxi
jernej has quit [Ping timeout: 252 seconds]
<bpi-user>
Hi! Is anybody familiar with the different kernel image formats and u-boot?
<bpi-user>
I have a few questions about that...
<bpi-user>
So far, I build and boot a "zImage" as described in the wiki. Since I wanted my kernel deployments to adhere more to the Debian standard, I was checking what files they use, etc.
paulk-collins has quit [Quit: Quitte]
formruga has joined #linux-sunxi
cosm has joined #linux-sunxi
mzki has quit [Quit: leaving]
bwarff_ has joined #linux-sunxi
<bpi-user>
One thing I stumbled upon was "vmlinuz" file Debian uses. On a lot of kernel development related pages/posts, it says that the vmlinuz file is created with make bzImage and then just renamed. At the same time bzImage is referred to as the "big" zImage for larger kernel images that don'T fit into the traditional 640kb boundary.
<bpi-user>
However, the wiki recommends building a zImage. And since the resulting image is clearly larger, I'm wondering if I should actually use make bzImage instead. Nevertheless, the generated zImage works absolutely fine.
p1u3sch1 has quit [Ping timeout: 268 seconds]
bwarff has quit [Ping timeout: 250 seconds]
<bpi-user>
So this is all a bit confusing. Does anybody know, what the image format is, that Debian actually builds for their ARM multiplatform kernels?
yann|work has quit [Ping timeout: 250 seconds]
buZz has quit [Ping timeout: 250 seconds]
<bpi-user>
Another thing that keeps me wondering is the "load address" for the device tree blob and the kernel image used in the u-boot script.
mosterta has quit [Ping timeout: 240 seconds]
mosterta has joined #linux-sunxi
adj_ has quit [Ping timeout: 268 seconds]
buZz has joined #linux-sunxi
<bpi-user>
The wiki already lists two different sets of addresses depending on whether you read the "Mainline Kernel Howto" or the page "Mainline U-Boot".
buZz is now known as Guest1050
<bpi-user>
One uses 0x46000000 for zImage and 0x49000000 for the dtb, while the other page says 0x42000000 and 0x43000000.
<bpi-user>
But if you look at the Debian wiki, you get yet another option: 0x43000000 for the dtb and 0x47000000 for the kernel.
<bpi-user>
Where do all these differences come from?
Guest1050 has quit [Read error: Connection reset by peer]
buZz_ has joined #linux-sunxi
yann|work has joined #linux-sunxi
khuey|away is now known as khuey
buZz_ is now known as buZz
adj_ has joined #linux-sunxi
cosm has quit [Ping timeout: 240 seconds]
ricardocrudo has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
cosm has joined #linux-sunxi
zoobab has quit [Remote host closed the connection]
zoobab has joined #linux-sunxi
khuey is now known as khuey|away
Keziolio has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
bwarff_ has quit [Quit: Leaving]
ganbold has joined #linux-sunxi
kelvan has quit [Quit: No Ping reply in 180 seconds.]