<granite_crusher>
pendrive is not bad, if to plug out one and replug other it will get mounted
<arokux2>
granite_crusher: hm.. let me clarify. you can mount each of the pendrives if only one of them is plugged in. however if two are plugged in you cannot mount the second one?
<granite_crusher>
arokux2: no, not one but only two
<granite_crusher>
and 3rd can't be mounted
<granite_crusher>
even dmesg reports it got pluged, and says it is sdc sdc1
<granite_crusher>
but same do <blkid> it shows just two from 3
<granite_crusher>
arokux2: I should test it in kernel 3.4, it is possible that problem can be on usb onboard hub
<arokux2>
granite_crusher: hm.. possible.
<arokux2>
granite_crusher: if you connect that third hub, everything works?
<arokux2>
if you connect it alone?
<granite_crusher>
arokux2: yeah first two works
<granite_crusher>
arokux2: oh you mean that way, yeah
<arokux2>
granite_crusher: ok. do you have external usb hub?
<granite_crusher>
arokux2: no I dont
<arokux2>
granite_crusher: ok, otherwise if you had a powered usb hub you could have tried to connect three pendrives to it, but ok.
<granite_crusher>
arokux2: I have SD with debian and kernel 3.0 I just will test there
<arokux2>
granite_crusher: I'll ask Tsvetan from Olimex if he thinks the power won't be enough for 3 pendrives.
<arokux2>
granite_crusher: oh, perfect.
<granite_crusher>
arokux2: I also thought it could be power
<arokux2>
granite_crusher: hm.. wait. do you actually have a partition on that third pendrive?
<granite_crusher>
but, have schematics there it is shown that it is 1000mA, (the host is intended on one of 4 chanels have wifi so it is powerfull enought)
<granite_crusher>
arokux2: 3td pendrive is ok, if I mount it first or second it gets mounted
<arokux2>
granite_crusher: ah, you have. i see.
<granite_crusher>
the rule is simple as jungle rule - who's first!
<arokux2>
:)
<arokux2>
granite_crusher: ok, 3 pendrives.. weird. please tell me you findings once you tried legacy kernel
Gerwin_J has joined #linux-sunxi
<arokux2>
granite_crusher: alsamixer and jack need to be installed, they are not in that rootfs I supplied to you. but you better test them after you have a distro on a usb stick mounted as rootfs
<granite_crusher>
arokux2: blkid gets all 3
<arokux2>
granite_crusher: on legacy kernel?
<granite_crusher>
arokux2: but most funny thing is that it is not sda1 sdb1 sdc1 but... uba1 ubb1 ubc1
<granite_crusher>
arokux2: yeah on kernel... how to check exactlly?
<arokux2>
uname -a
<granite_crusher>
3.0.52+
<arokux2>
granite_crusher: you cannot mount usb stick as rootfs because the driver wasn't loaded yet.. so the kernel didn't know about /dev/sda1 yet. we need to find a way to force it to enumerate all usb devices first.
<granite_crusher>
arokux2: probally initrd...
<arokux2>
granite_crusher: should be possible to deal without it.
<arokux2>
granite_crusher: and usb support is built-in any way
<arokux2>
granite_crusher: initrd is used to add flexibility -- so you do not build stuff into the kernel
<granite_crusher>
arokux2: hope these findings will help, I think it is time to sleep
<arokux2>
granite_crusher: yes of course, very helpful indeed. good night!
granite_crusher has quit [Quit: Page closed]
\\Mr_C\\ has joined #linux-sunxi
ykchavan has quit [Ping timeout: 252 seconds]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
arokux2 has quit [Remote host closed the connection]
<akaizen>
is anyone good with Allwinner android here?
Gerwin_J has quit [Quit: Gerwin_J]
awafaa has quit [Ping timeout: 260 seconds]
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
TheSeven has quit [Read error: Operation timed out]
TheSeven has joined #linux-sunxi
\\Mr_C\\ has quit []
awafaa has joined #linux-sunxi
hramrach has joined #linux-sunxi
rellla has joined #linux-sunxi
rellla has quit [Client Quit]
forcev is now known as FunkyPenguin
FunkyPenguin has quit [Changing host]
FunkyPenguin has joined #linux-sunxi
wingrime has joined #linux-sunxi
rz2k has joined #linux-sunxi
<oliv3r>
next set of pinctrl patches work
Black_Horseman has quit [Ping timeout: 260 seconds]
<arokux2>
granite_crusher: I know what you should do to wait for usb stick popup with your /dev/sda1
<arokux2>
granite_crusher: Add root=/dev/sda1 rootwait to your cmdline.
<granite_crusher>
yeah I saw in your wiki section, nice
<granite_crusher>
well, if to continue with this usb error in u-boot
<granite_crusher>
I get it just with two devices - one is semi pro grade (M-audio Fast track pro) usb soundcard, other is also kind of audio equipment - usb MIDI keyboard (CME M-key v2)
<wingrime>
oliv3r: ping
<arokux2>
granite_crusher: I see. are they both full speed?
<granite_crusher>
arokux2: low-speed mouse, keyboard or high speed webcam or eth-usb dongle gets ok and visible with <usb tree>
<arokux2>
granite_crusher: I see. (might be a bug in U-Boot usb stack too.)
<granite_crusher>
arokux2: I just dmsg'ed it on pc, yep bowth is full-speed
diego71_ is now known as diego71
<arokux2>
granite_crusher: where do you know mouse is low-speed? checked it?
<granite_crusher>
arokux2: in addition, u-boot can read from 3 pendrives at once
<arokux2>
granite_crusher: other thing.. blkid may output wrong things. to verify 3 pendrives, try to mount all of them.
<granite_crusher>
arokux2: I checked it with dmesg
<granite_crusher>
on pc
<granite_crusher>
arokux2: I tried and it failed
<arokux2>
granite_crusher: ah, nice, so only full speed devices won't work.
<granite_crusher>
arokux2: identical behaviour as blkid
<wingrime>
mnemoc: when you last time saw Ithamar ?
<arokux2>
granite_crusher: what was the error when you tried to mount it?
<arokux2>
granite_crusher: is it in that dmesg you sent me yesterday?
<granite_crusher>
arokux2: no it is not in that log
<granite_crusher>
arokux2: one liner
<granite_crusher>
mounting /dev/sdc1 on /mnt/apacer failed: No such file or directory
<n01>
tm512: nice post on reddit ;)
<arokux2>
granite_crusher: hm.. was there /dev/sdc1, have you checked?
hramrach has quit [Ping timeout: 240 seconds]
<granite_crusher>
arokux2: dmesg showed it got plugged and that it is sdc
<granite_crusher>
but neither blkid can see it neither can it be mounted
<arokux2>
granite_crusher: yeah, and then there was also line sdc: sdc1, have you noticed?
<granite_crusher>
yeah
<arokux2>
granite_crusher: so I wonder if there was /dev/sdc1 device file.
<granite_crusher>
arokux2: I am sending you log excerpt
<choko>
i checked my mini usb port is only for power
hramrach has joined #linux-sunxi
<granite_crusher>
arokux2: where do it save it?
<granite_crusher>
arokux2: SD card, SD fat partition, or USB partition?
<arokux2>
granite_crusher: sd card
<granite_crusher>
cool
<arokux2>
granite_crusher: there is a special place reserved for environment
<arokux2>
choko: so you cannot use it to connect a usb device?
<choko>
no i can't do that
<arokux2>
choko: i see.. :(
<arokux2>
choko: btw, you compiled your kernel by yourself?
<choko>
any other options ?
<choko>
yes compiled by myself
<choko>
but i also used Fedor wich downloaded
<choko>
Fedora
<granite_crusher>
arokux2: I think after usb start I should force u-boot wait a bit, how to do that?
<choko>
If you have any other compiled version for a10s give a link ;)
<arokux2>
granite_crusher: next command won't start till the last finishes, so no need to do smth
<arokux2>
choko: yep, you said u used fedora and 3.4.61.. and I was surprised later because that fedora image is rather old. but now interesting question comes. does it work the same under fedora kernel (which version is it, btw?) and 3.4.61 kernel?
<arokux2>
choko: ok.. but what kernel version is inside? just run: uname -a
<choko>
but i can't login right now, somthing fuckup with password
<arokux2>
choko: oh shit
<choko>
i mounted on my linux and changed /etc/shadow but still don't work
<choko>
ah btw this ofcourse booting from my sdcard not nand partition
<granite_crusher>
arokux2: You can delete that problem 2 of 3 usb, there is no /dev/sdc* files in this buildroot initramfs
<choko>
maybe this is a problem
<arokux2>
granite_crusher: sorry?
<arokux2>
granite_crusher: why should I delete if there is no /dev/sdc1? (you can edit it yourself!)
<arokux2>
choko: why have you changed /etc/shadow?! it is where the passwords are stored.
<granite_crusher>
arokux2: I found that in /dev/ there is plenty of sda* (1 2 3 ... 9) sdb*(1 2 ... 9) but no sdc
<choko>
yes i changed to password which i knew
<granite_crusher>
arokux2: I mean in wiki, that ppl wouldnt think there is something wrong
<arokux2>
granite_crusher: why so many sda*? this is not good
<granite_crusher>
I think it is because of buildroot
<arokux2>
granite_crusher: .. no idea.
<arokux2>
granite_crusher: you can get rid of this buildroot and try to put you rootfs on usb stick
<arokux2>
granite_crusher: do you have debian rootfs?
<granite_crusher>
arokux2: that initramfs have lots of devices... If they would be real ... http://sprunge.us/iJIR
<arokux2>
granite_crusher: some video* too!
<arokux2>
granite_crusher: no idea. i think it is best to switch to some distro. you'd nee a sane package management too.
<granite_crusher>
arokux2: is there difference where will be my uImage and dtb, can it be just in / or should I copy it to /boot/?
<granite_crusher>
I have deboostraped debian, which worked with 3.4 kernel
rz2k has joined #linux-sunxi
<n01>
granite_crusher: are you using devtmpfs?
<granite_crusher>
devtmpfs?
<n01>
15:01 < granite_crusher> arokux2: I found that in /dev/ there is plenty of sda* (1 2 3 ... 9) sdb*(1 2 ... 9) but no sdc
<arokux2>
granite_crusher: nope, you can put your kernel where ever you want. however..... i think it is better to put it at some place where you have a shared access to it.
<n01>
it seems like you are not using devtmpfs
<arokux2>
granite_crusher: if you later would like to change your kernel and try things out, you wouldn't like to mess up with usb sticks
<arokux2>
granite_crusher: I recommend you get your usb2ethernet working and set up tftpserver (very easy)
<granite_crusher>
n01: Ichecked my kernel config it is enabled
<n01>
granite_crusher: are you using udev/mdev?
<n01>
or a static dev allocation map
<arokux2>
n01: whatever is in buildroot...
<granite_crusher>
n01: where to check it?
<n01>
arokux2: in buildroot it is configurable obviously
leowt has quit [Remote host closed the connection]
leowt has joined #linux-sunxi
<arokux2>
do you know cheap-shipping online shop for connectors & stuff?
<granite_crusher>
arokux2: me?
<arokux2>
anybody
<Sonicadvance1>
digikey
<arokux2>
Sonicadvance1: +18 EUR
<Sonicadvance1>
oh
<jelly-home>
arokux2: cheap-shipping to which country
<arokux2>
jelly-home: Germany
tzafrir has quit [Ping timeout: 264 seconds]
<arokux2>
granite_crusher: ah! still there?
<arokux2>
granite_crusher: just realized: the file /dev/sdc1 is not created because it's not in that static list of device files in buildroot
<arokux2>
granite_crusher: so it should work, I think --> removing it from wiki
<n01>
Turl: ping
<granite_crusher>
arokux2: good
<granite_crusher>
arokux2: I changed in my config of kernel rootdelay=10 into rootwait as you suggested in wiki... no luck, i get kernel panic in same place... maybe usb should be /dev/uba1 not sda1?
<arokux2>
granite_crusher: oh wait.. so you had rootdelay=10 already? rootwait just means to wait indefinitely
<arokux2>
granite_crusher: so as it hasn't waited i assume you change hasn't had any influence..
bamvor has quit [Ping timeout: 245 seconds]
bamvor has joined #linux-sunxi
<granite_crusher>
arokux2: maybe I should force it to use these in kernel by setting <Kernel command line type> into "always use default..."?
<arokux2>
granite_crusher: do not know anything about that. I normally set bootargs in u-boot
<granite_crusher>
arokux2: I am stupid... to use bootargs in uboot it is much easier than to recompile kernel....
<arokux2>
granite_crusher: now you know it... :)
<arokux2>
granite_crusher: so if you want to continue to hack you'd need to setup things so everything is automatic, only minimal interaction. I can give you tips later. I can boot different kernel each 10 sec, i think :)
<granite_crusher>
arokux2: cool
<aep>
anyone knows how to rotate the lcd output?
<granite_crusher>
arokux2: I think after console=ttyS0 I should add ",115200" because now I get just
<granite_crusher>
Starting kernel ...
<granite_crusher>
arokux2: and USB led is flashing (means it is used
<arokux2>
granite_crusher: wait a bit
<arokux2>
granite_crusher: we should have added earlyprinkt probably.. (not sure)
<arokux2>
granite_crusher: but you will get a shell later if it works
<n01>
you have to enable earlyprintk on the right tty
<arokux2>
granite_crusher: maybe there is something like UUID to /dev/sd* mapping you can set, then you can use /dev/sd*
<granite_crusher>
arokux2: I counted about 200 tty* in /dev/.......... what a hell?
<naobsd>
arokux: is on board USB wifi powered properly? I guess it's controlled by GPIO
<arokux2>
naobsd: do not know, but i do same gpio trick for both controllers..
skoti has joined #linux-sunxi
<granite_crusher>
arokux2: I remember somewhere in the internets were instructions how to use /dev/disk/by-uuid/<UUID> instead of /dev/sd*
<naobsd>
arokux: what I said is not about host controller, I guess there is board specific GPIO pin to give power for on-board USB wifi... is it detected?
<naobsd>
arokux: well... it seems there is no information :( so it should work w/o any special handling for power. if on-board wifi can be found, it should be powered
<mouchon>
i try to refactor my i2c patch to avoid ugly code. But still have a choice problem. should i use inline function or macro the kernel doc is not clear for me
jacq has joined #linux-sunxi
<arokux2>
naobsd: can I measure with multimeter? I've tried each pair of pins and for some there were 3.3V, so I assume it is powered, right?
<arokux2>
hi mouchon, nice to see you here.
<arokux2>
mouchon: to be honest I do not know... but there was some discussion here about inline vs define
<naobsd>
arokux: then it should not be power issue, sorry
<naobsd>
arokux: did you tried USB device which has EP more than 1?
<arokux2>
naobsd: usb2ethernet for example?
<naobsd>
arokux: probably yes
<arokux2>
naobsd: yep, it works.
<arokux2>
naobsd: if it is power - than it's good. you know it works in sunx-3.4. it is not board specific kernel. so the power enablement should come from fex, right?
<arokux2>
hipboi: am I right?
<arokux2>
hipboi: we're talking about the power supply to the on-board wifi module
<naobsd>
arokux: if it works with 3.4, board specific power thing should not be needed because it seems there is no such information in fex
arokux2 has quit [Remote host closed the connection]
arokux2 has joined #linux-sunxi
<rz2k>
arokux2: oh
<rz2k>
dont remember, do you have a multimeter?
<wingrime>
who is Дмитрий Снежинский?
<arokux2>
rz2k: yes, I have one!
<rz2k>
then boot device to any kernel where you have everything working and find +5V
jemk has joined #linux-sunxi
<arokux2>
rz2k: I can find only 3.3V. is it bad?
<rz2k>
probably this module needs 3.3v regulator
<rz2k>
and has supply of that sort
<rz2k>
honestly, I have no experience with these micro wifi modules
<arokux2>
:$
<rz2k>
I mean in my projects, so I could tell you exactly whats happenning
<rz2k>
you should trace the board and find where 3v3 from wifi module is connected. probably to transistor that enables this regulator, which is controlled by gpio
<rz2k>
or read the 3.4 wifi code
<rz2k>
I bet it has something like that somewhere
<arokux2>
rz2k: mainline driver works with wifi...
_enrico_ has joined #linux-sunxi
<arokux2>
rz2k: so there is nothing special that allwinner plugged in, afaik
<arokux2>
rz2k: I was trying to aks a USB maintainer..
buZz has quit [Read error: Connection reset by peer]
buZz has joined #linux-sunxi
sdboot has joined #linux-sunxi
hipboi has quit [Quit: Leaving]
<sdboot>
How do I boot from an SD card on a tablet that always boot from NAND first? Boot order is SD0, NAND, SD3, right?
<wingrime>
sdboot: yes
<wingrime>
sdboot: but be sure you use sd0 not sd3
<sdboot>
I think that's the problem. If SD3 is connected, is there any way to boot a custom Linux image from SD?
<wingrime>
sdboot: kill nand
<wingrime>
sdboot: just short some data lines
<wingrime>
sdboot: boot will be failback to sd3
<arokux2>
wingrime: do you have Mele A1000?
<wingrime>
arokux2: no
<sdboot>
No A20 A70x
<wingrime>
sdboot: you can kill nand boot signature , erase first sectors
<sdboot>
I have a backup of the NAND partitions, so I should be able to recover it right?
djahma has joined #linux-sunxi
<wingrime>
sdboot: you can simply short nand ic wires when boot
rellla has quit [Remote host closed the connection]
<djahma>
hi there, has anyone managed to get A10 wifi working? I've got a tablet I just can't manage to connect to internet. currently compiling sunxi 3.4 branch for more modules but often get errors
Cubear has quit [Quit: leaving]
geecko has quit [Quit: Quitte]
<rz2k>
arokux2: no idea really
<rz2k>
seems like errors on usb bus
<rz2k>
hardware ones
Vespine has joined #linux-sunxi
Vespine is now known as Cubear
<Turl>
n01: pong
_enrico_ has quit [Read error: Connection reset by peer]
jemk has quit [Remote host closed the connection]
<arokux2>
rz2k: yeah.. do you have *any* idea how can I track the difference between two behaviors?
<arokux2>
Turl: do you plan to push PLL6 soon?
sdboot has quit [Ping timeout: 250 seconds]
_enrico_ has joined #linux-sunxi
<n01>
Turl: rtc driver is almost the same for a10 and a20 but for some constants. To distinguish between the two I'm using two different of_device_id
<n01>
there is any other way in mainline to do that?
<n01>
in sunxi-3.4 there is sunxi_is_sun7i()
<arokux2>
n01: do you have a wifi dongle? :p (don't remember if I asked you..)
<n01>
arokux2: yeah
<arokux2>
n01: could you test my tree with usb support please? you might have heard there are some problems with on-board wlan
<n01>
"on-board wlan" ??
<arokux2>
n01: yes, why are you surprised?
<n01>
are you talking about cb2+
<arokux2>
n01: no, I have another board: Mele A1000
<n01>
hoooo, now it makes sense
<arokux2>
n01: but I would like you to test wifi dongle, so that I know it is not special to wifi..
<arokux2>
n01: I suppose it should work.
<n01>
arokux2: I'll put it in TODO list
<arokux2>
n01: I can test your rtc patch on Mele, it is sun4i
Gerwin_J has joined #linux-sunxi
<n01>
yeah the problem is that one :) I want to finish with this driver asap
<arokux2>
n01: no prob
<arokux2>
n01: same here :D
<Turl>
n01: just use two diff compatibles, and pass the constants with that
<arokux2>
Turl: I'm just asking if the mainline works the way it is described in comment to that function.
<arokux2>
and the limitation of apb is 150Mhz. for usb connecting,
<arokux2>
* the frequency of ahb must not lower than 60Mhz.
<granite_crusher>
arokux2 and Turl: cpufreq shouldn't work in mainline because there is no AXP drivers
aexl has joined #linux-sunxi
<aexl>
moin.
<aexl>
does anybody have a mele m5. and knows if it got a uart interface?
<arokux2>
aexl: oh, we'd love to have some mele m5 pictures....
<Turl>
arokux2: cat clk_summary and see for yourself? :) dunno
<Turl>
granite_crusher: you can get along with no axp and scale just the freq and not the voltage
<Turl>
but it's half the fun :)
<arokux2>
Turl: ah, right.. thanks
<aexl>
arokux: hm. this looks comprehensive: androidpc.es/blog/2013/05/10/mele-m5-con-soc-a20-dualcore-en-oferta-en-su-tienda-oficial
<arokux2>
aexl: the pictures of the board inside..
Gerwin_J has quit [Quit: Gerwin_J]
<arokux2>
Turl: "the limitation of apb is 150Mhz. for usb connecting" do you think its the upper or lower bound?
<Turl>
arokux2: you're reading that wrong
<Turl>
" for usb connecting,
<Turl>
* the frequency of ahb must not lower than 60Mhz."
<arokux2>
*sigh* it is 168Mhz now..
<brain_>
ok this is just annoying, I changed my bootargs in u-boot to reduce the bootdelay and now the device just loads boot0 after attempting to start the kernel...i don't get it.
<brain_>
i'm sure its just not finding anything in nand but why would a simple change like that cause this? should I try to upgrade u-boot?
<brain_>
from my understanding their is no u-boot source with nand support tho?
<brain_>
I'll be back, hopefully someone can help out here. gotta boot into crap windows to livesuit it.
<arokux2>
brain_: yes, our u-boot does not support nand
<brain_>
:( sucks.
<granite_crusher>
arokux2: I am using your tree, so I should ask you, why rtc doesnt work? it is written that clock drivers was merged into 3.10 and I2C (rtc is atached throught it) at 3.11.
<arokux2>
n01: ^ <--- this guy is working on this driver afaik, my tree is based on the last stuff, dunno.
<Turl>
granite_crusher: what device?
<arokux2>
Turl: A13
<Turl>
granite_crusher: most devices don't have an external i2c rct though
<granite_crusher>
Turl: board or clock?
<Turl>
granite_crusher: hm?
<Turl>
granite_crusher: if your device has you probably just need to add the info to the device tree
<granite_crusher>
Turl: it is soldered on A13-olinuxino... device tree hmm...
brain_ has quit [Remote host closed the connection]
<granite_crusher>
is there somethere info how to make stuff in these device trees?
<arokux2>
granite_crusher: but maybe take a look at other sunxi dts..
wingrime has quit [Read error: Operation timed out]
<Turl>
granite_crusher: let me look at the O-A13 schematics
<granite_crusher>
arokux2: good idea, copy paste and modify :)
wingrime_ has quit [Ping timeout: 248 seconds]
<granite_crusher>
arokux2: by the way I got booting with UUID, just not exactly as links you sent, and its kind tricky it needs hybrid partition table MBR and GPT in one (GPT for kernel, MBR for u-boot)
wingrime has joined #linux-sunxi
<arokux2>
granite_crusher: ok, good that you figured it out. have you configured network?
wingrime_ has joined #linux-sunxi
<granite_crusher>
arokux2: still not, I am trying to do it now
<arokux2>
granite_crusher: ok let us know in case of problems..
<Turl>
granite_crusher: I'll make a patch for the rtc if you want, looks like it's already supported kernel wise
deasy has joined #linux-sunxi
<granite_crusher>
Turl: you mean that rtc on chip is supproted in kernel?
<granite_crusher>
at least I thought so
ZetaNeta has quit [Remote host closed the connection]
<granite_crusher>
I enabled it while in config
ZetaNeta has joined #linux-sunxi
<Turl>
granite_crusher: yes, you just need to declare it on the dt
<granite_crusher>
Turl: cool, should I try to do it? (patch, I never did it and I am not good in git, but would be great to learn it)
<arokux2>
granite_crusher: yes, this is a really good task to start how to do a patch
<arokux2>
granite_crusher: if you like to learn it - go for it
<hno>
gpio_set_one_pin_driver_level sets the I/O drive strength. Don't know what levels are available.
<arokux2>
hno: I wasn't asking about that one
<mnemoc>
arokux2: ssh arokux@sunxi.org ...... SDK/ is dl..../SDK and public_html os dl..../users/arokux
<arokux2>
mnemoc: thanks
<hno>
gpio_write_one_pin_value set the GPIO output value for a pin.
<hno>
arokux2, I know you didn't ask for the _drive one, but it's very closely related to the _pull one.
<wingrime_>
mnemoc: tryed , but ....
<arokux2>
hno: ah, ok, I've thought you have mixed it with the other one I've asked about, sorry.
<hno>
arokux2, see the PIO chapter in the user manaual. These all map directly to the corresponding fields for the pins in PIO.
<arokux2>
hno: another question. how should I go about different gpio pins needed for different boards to enable usb?
<arokux2>
hno: should there be defines per board, or how is it done?
<hno>
arokux2, it's just different GPIO pins for VBUS power control. Noting strange. What do you mean exactly? For mainline it goes into DT. For 3.4 it's in script.bin.
<arokux2>
hno: yep, my question is where it goes in u-boot.
<arokux2>
hno: sorry, wasn't clear i'm talking about u-boot now..
<hno>
Ah, there... a define with the GPIO number that needs to be enabled when enabling u-boot. can easily be set in boards.cfg .
focus_it has joined #linux-sunxi
<arokux2>
alright. thanks hno
drachensun has quit [Read error: Operation timed out]
<arokux2>
hno: how are you doing?
<n01>
granite_crusher: what about rct
<n01>
*rtc
<arokux2>
hno: btw, mainline rtl driver works just fine with wlan
akaizen has joined #linux-sunxi
<tgaz>
yay. musb gadget serial console working after FEL boot.
<arokux2>
tgaz: you've added it?
<arokux2>
tgaz: just curios, i'm not in context
<tgaz>
arokux2, no, debugged it. jukivili added it
<tgaz>
i added a musb_writeb(mbase, MUSB_FADDR, 0); in musb_g_reset() to get it to work
<tgaz>
the musb driver assumes it starts up with FADDR=0 it seems
drachensun has joined #linux-sunxi
<hno>
arokux2, I am a bit stressed at the moment, preparing last pieces for product launch.
<arokux2>
hno: yeah, I know that is why i'm asking. hope everything goes as planned.
<hno>
arokux2, will know in about 24 hours..
<arokux2>
hno: :)
wingrime_ has quit [Read error: Connection reset by peer]
akaizen has quit [Remote host closed the connection]
rzk has joined #linux-sunxi
rz2k has quit [Ping timeout: 248 seconds]
skoti has quit [Quit: leaving]
massi has joined #linux-sunxi
<granite_crusher>
n01: well I got error while booting mainline kernel about rtc, but looks it is problem what there is no rtc defined in device tree, and I am going to try add it
rzk has quit []
<Turl>
granite_crusher: yeah but it's a different rtc :) yours is an external one
<Turl>
n01 is working on the SoC-internal one
<n01>
granite_crusher: which kernel on what boaord
<Turl>
n01: A13 olinuxino iirc, has an i2c rtc from nxp
<n01>
hooo, ok mine is internal for sun4i/7i
<n01>
granite_crusher: good luck with that :)
<n01>
anyway driver is done. I need to test it again
<arokux2>
hno: I cannot understand something. if i won't set gpio to output 1 in 3.4, usb hub won't enumerate wlan adapter, however if you won't set gpio to 1 in mainline, wlan adapter will be enumerated regardless
<arokux2>
hno: oh, forget it, it is enabled by somebody already
<granite_crusher>
arokux2: ethernet is working :) (I succesfully apt-get update)
<arokux2>
granite_crusher: cool. now set up tftp and forget about plugging and unplugging of a usb stick
focus_it has quit [Quit: Leaving]
<granite_crusher>
arokux2: I have bad feeling about usb on that board... it have led which in both legacy and mainline kernel keeps lighting while it doesn't do so on laptop, (even if used as live usb), can it be result of that USB_EN open?
<granite_crusher>
arokux2: I am talking about usb storage
<arokux2>
granite_crusher: no idea, sorry
<arokux2>
granite_crusher: led will never be on on laptop?
<granite_crusher>
arokux2: no, just at moment it is read
<granite_crusher>
or write
<arokux2>
granite_crusher: hm.. I see, you'd need to ask Tsvetan
<arokux2>
mripard: how do you think, who can set GPIO output 1 if not your code?
<arokux2>
mripard: ignore.
<n01>
who is Carlos Quijano?
<arokux2>
hm.. do you guys know where gpios are touched in 3.4?
<arokux2>
except of some obvious places..
aexl has quit [Quit: Leaving.]
<hno>
arokux2, 3.4 kernel is quite dirty.. PIO is touched directly in too many places. But most are using the sys_config.c functions discussed earlier, or the implicit one requesting gpios which sets them to what is in script.bin.
<arokux2>
hno: I've found it. they clear it in *_request func
<arokux2>
hno: I do not know what to do.. I have 200 lines of code which works in 3.4 but fails in mainline
massi has quit [Quit: Leaving]
<arokux2>
hno: maybe this is some regression in mainline in ehci-hcd.. I have no idea how I should track it down now
tinti has joined #linux-sunxi
_enrico_ has quit [Quit: Bye]
wingrime has quit [Ping timeout: 240 seconds]
akaizen has joined #linux-sunxi
<Turl>
granite_crusher: did you get rtc working? :)
<Turl>
n01: dunno :)
akaizen has quit [Remote host closed the connection]
<n01>
I'm writing a new defconfig and scripts for mainline kernel in buildroot
<n01>
what time is there Turl
<Turl>
n01: 8PM
<Turl>
n01: maybe in #buildroot someone recognises him
akaizen has joined #linux-sunxi
<Turl>
n01: the guy is apparently spanish though, so 1AM for him :)
<n01>
yeah, same here :)
<Turl>
n01: btw, what device specific stuff does buildroot need?
<Turl>
I've been using it for quite a while now
<Turl>
and don't recall needing any black magic :)
<n01>
Turl: just a new defconfig and a couple of script for making the sd
<arokux2>
is there something like hrtimers in mainline for sunxi?
<Turl>
n01: ah, so it's uboot integration, nice
<Turl>
arokux2: yeah, maxime sent hrtimer patches like this week
<Turl>
arokux2: I've picked them in sunxi-devel if you want to test drive them :)
<arokux2>
Turl: I really have no idea what I can test :$
<Turl>
arokux2: I asked the same to maxime, he said that if it boots it's working :)
<arokux2>
Turl: I mean about usb.......
<Turl>
arokux2: ah
<Turl>
you think it's latency sensitive?
<Turl>
arokux2: well, it's worth a shot I suppose
<arokux2>
Turl: well... you know sometimes I see such errors in 3.4 too, but then it restores and works.
<arokux2>
Turl: also, take a look here: drivers/usb/host/ehci-timer.c
<arokux2>
Turl: it uses hrtimers...
<arokux2>
Turl: Alan told it could be timing issue.
<arokux2>
Turl: i'm not sure these timers are used, though.
<Turl>
arokux2: go grab the hrtimer patches from lakml and give it a go then
<Turl>
the old timer is just 24Mhz, might not have enough resolution
<arokux2>
Turl: he has added them to everything except sun4i. is it a matter of adding support to dt?
<Turl>
arokux2: no, sun4i doesn't have hrtimers
<Turl>
the hw block is only present on sun5i+
<arokux2>
Turl: ok...
<Turl>
arokux2: I could give it a try on my sun7i though
<Turl>
is your tree up to date?
<arokux2>
Turl: yep
akaizen has quit [Remote host closed the connection]
<arokux2>
Turl: ehci-timer.c wasn't there at 3.4 times.
<arokux2>
Turl: but wait, what are you going to try? you do not have wifi module anyway
akaizen has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
<Turl>
hm good point
<Turl>
:P
<arokux2>
nobody wants to try out a wifi dongle on mainline, what a shame :(
<arokux2>
Turl: so sun4i timer has also resolution of 24Mhz?
<Turl>
arokux2: it runs with osc24M so it should
<Turl>
arokux2: I just remembered I have two ancient bluetooth USB thingies, they do the same as my soundcard
<Turl>
(ie, just raise 2 interrupts and do nothing, and render the port unusable until next reboot)
<arokux2>
Turl: you mean prevent usb from working?
<Turl>
yeah
<Turl>
I really think all of these things would work if we had OHCI support :)
<Turl>
my pendrive still works
<arokux2>
Turl: ... I can add OHCI, no problem, but why should I do it now?
<Turl>
arokux2: so you can distinguish between "doesn't work because there's no OHCI support" vs "doesn't work because EHCI is broken"? :)
<Turl>
arokux2: also, maybe wifi works in ohci only mode
<arokux2>
Turl: you can try to put these sticks with legacy kernel
<arokux2>
Turl: no wifi works on EHCI..
<Turl>
USB2 devices theorically work just fine on USB1 hosts
<Turl>
just like USB3 devices work on USB2 hosts
<Turl>
it'll just be slow :)
<arokux2>
Turl: maybe. you can easily comment out OHCI/EHCI (config won't help) in legacy 3.4 and see what happens.
<arokux2>
granite_crusher: still working?
<granite_crusher>
arokux2: trying to understand that device tree.... fex looked much more simple...