<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>
naobsd: yep, it works.
<naobsd>
arokux: probably yes
<arokux2>
naobsd: usb2ethernet for example?
<naobsd>
arokux: did you tried USB device which has EP more than 1?
<naobsd>
arokux: then it should not be power issue, sorry
<naobsd>
I should learn how to build/use mainline kernel...
<naobsd>
arokux: is there any a1000 internal photo?
<naobsd>
arokux: sorry, not sure
<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?
<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
<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?
<arokux2>
naobsd: do not know, but i do same gpio trick for both controllers..
<naobsd>
arokux: is on board USB wifi powered properly? I guess it's controlled by GPIO
<arokux2>
naobsd: I see. are u interested in testing a mainline a bit? I have a problem with on-board wifi, I wonder if it is because its on-board.
<naobsd>
arokux: can you tell me summary of devices which are working, or not working?
<naobsd>
well, I don't have NetBSD userland(rootfs) for now :(
<arokux2>
naobsd: can you try if it works with your cubieboard and netbsd?
<naobsd>
arokux: I have USB wifi dongle
2013-09-26
<arokux2>
naobsd, hi, you there? I have a problem with my USB driver. storage works, but USB WiFi won't. can you try if some USB WiFi module works in *BSD you are using? I do not know if *BSDs have support for wifi..
2013-09-14
<vaxholm>
naobsd, thanks.
<naobsd>
hmm
<oliv3r>
naobsd: wouldn't really care for running it, only to compare against it
<naobsd>
does anyone try 3.4 kernel from SDK2.0 for A20?
<naobsd>
if software is incompatible, driver or library need to be fixed. if hardware is incompatible, need more RE. from message on google groups, it sounds something need to be provided from allwinner, I felt strangeness
<naobsd>
ah, I see
<naobsd>
hno: thanks
<hno>
naobsd, there is plenty of blobs in the 3.3 kernel, but none that is relevant to CedarX.
<naobsd>
I think there is no binary blob in 3.3 kernel...
<naobsd>
I'm not sure missing == not ported yet, or == only binary blobs for 3.3 are available
<naobsd>
I guess they are talking about 3.4 kernel, I'm not sure
<naobsd>
(it was mentioned on cubieboard google groups)
<naobsd>
is there any missing driver for A20 to use libvdpau-sunxi? I can't find any detail about it
2013-08-16
<naobsd>
my files are just for example, I don't know if it's really useful for some specific purpose other than "it could be booted" :)
<soletti>
naobsd, right - ill try to boot your images later wheni get back home
<naobsd>
s/from non-USB miniB port/from power connector/
<naobsd>
soletti: and if you used v1.04 script.bin on my site, you have to supply power before starting kernel from non-USB miniB port.
<naobsd>
soletti: if you used my uImage, it's lichee linux-3.3 kernel, you need to set machid to f35. otherwise you can't see anything after "Starting kernel..."
<soletti>
right now im trying to boot using naobsd image from androtab.info/cubieboard2
<naobsd>
soletti: sorry, which file are you using from my site? I said please use my u-boot but you said you're using your own u-boot
<soletti>
naobsd, using those binaries i get the same error if i build mine own kernel/uboot: ERROR: Failed to allocate 0x1000 bytes below 0x0.
<naobsd>
I just added "setenv ..." on my web site ;)
<naobsd>
it's time to make "community kernel" which just has proper machid ;)
<naobsd>
anyway, sorry for taking your time for my bad brain
<naobsd>
if I can modify Makefiles easily ;)
<naobsd>
single target per board, it builds full u-boot.bin and 2 spl.bin
<naobsd>
probably I like single full u-boot.bin ;)
<naobsd>
if I don't need mmc spl, I can use u-boot.bin built by fel target... I understand know :(
<naobsd>
I used u-boot.bin built by non-fel target, but
<naobsd>
ah
<naobsd>
anyway, SUNXI_EMAC word is not necessary in _FEL line
<naobsd>
I understand right way now...
<naobsd>
only tools/ and spl/ have .o
<naobsd>
I just do it
<naobsd>
surely no emac.o under spl/drivers/
<naobsd>
(I did "make mrproper" at 1st)
<naobsd>
just "make" after "make cubieboard2_fel_config" does some unnecessary thing? there is ./drivers/net/sunxi_emac.o
<naobsd>
hmm, emac.o is build, but not linked, right?
<naobsd>
yes, I read your allwinner-info too
<naobsd>
I think SUNXI_EMAC word can be removed from _FEL in boards.cfg
<naobsd>
anyway
<naobsd>
I always copied mmc one instead of fel one compiled on different directory :(
<naobsd>
really sorry
<naobsd>
yup
<naobsd>
yes, 11KB is fine, I copied 22KB (probably not for fel) spl bin. I wonder why I believed there is 8KB limit :(
<hno>
naobsd, there likely is some KB that can be shaved off, the early fel boot binaries wer about 7KB in size. But as 11KB well within allowed size I have not cared to try to minimize the FEL SPL further.
<naobsd>
really sorry
<naobsd>
please don't mind, my brain was too bad
<naobsd>
yes
<hno>
naobsd, FEL SPL for cubieboard & cubiebord2 is almost the same size.
<naobsd>
(sorry, I don't have enough time to write something in wiki)
<naobsd>
bin for cubieboard1 is smaller than 8K so my insane fel binary can handle it
<naobsd>
I never said hang after DRAM: is problem
<naobsd>
oliv3r: I said I pushed bin for cubieboard1 into cubieboard2
<naobsd>
I thought 11kb is issue, but hno confirmed it's ok
<naobsd>
oliv3r: hno's wip/a20. but it's not u-boot source issue. fel is not working properly
<naobsd>
but "fel write 0x2000 11kb-bin" never complete
<oliv3r>
naobsd: what a20 u-boot branch are you using?
<naobsd>
I can do "./fel write 0x2000 bin/fel-boot-cubieboard.bin; ./fel exec 0x2000", I can see "DRAM:" in serial console (then it hangs, probably expected result)
<naobsd>
hmmmm
<naobsd>
fel ver works fine: AWUSBFEX soc=00165100(unknown) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000
<hno>
naobsd, "fel clear 0x4000 1" also works fine for me.
<naobsd>
connect USB miniB while pushing fel button