On 07/02/13 19:28, minux wrote:
On Mon, Jul 1, 2013 at 7:20 PM, Artturi Alm <artturi....@gmail.com> wrote:
So, i found out that the docs i have don't include
sd/mmc controller register definitions etc., only the overview.
which lead me to fix ehci and now it might boot, but
i cant figure out how to cross-build release, if it's even
the cross-distrib target in Makefile.cross might help you (cross-gnu
doesn't work,
so getting a native toolchain cross compiled needs more work)
alternatively, when i last tried to bring up the beagle port on Pandaboard
ES,
i used the lastest armish binary sets and although not all programs work
(mainly
due to using SWP on Cortex-A9) the system could boot into multi user
successfully.
after it boots up, you can rebuild /usr/src/lib/librthread, and replace the
library
so that perl runs and then you have a working system to do a full native
build.
supported, and if not, what else can i do?
in short: i dont know how to build userland etc. to be placed
on the umass which attaches so i it would boot properly..
i copied beagle/conf/RAMDISK into allwinner and it does build,
and is about 1mb bigger, but it panics on error opening disc.
and honestly, im not sure if it freezes now where it does because
there is no sd0b on that old stick, didnt bother with it since there's
no /bin etc. anyway, but userland is what i need i think :)
Thanks, armish sets got it further, it does however still freeze quite
early, while running /etc/rc.
i was hoping to be able to stay within /allwinner, but now i think doing
so would mean waiting for devs to fix beagle on other boards than
Pandaboard ES, which i _guess_ to be pmap related issue atm..
me trying to fix anything in arch/arm is like working blind, i have no
other boards than cubie to test on.
besides that, i have a cause of concern that this might be wasted effort
anyway...
i spent some days again working on interrupt and timer handling to fix
errors from first revs that seemed to work without DEBUG, hiding the
errors away from dmesgs i've sent, now it doesn't print timeout delayed
warnings anymore nor
mutex held on enter panics or anything.
this made in china SoC has excellent docs avail, not.
now i don't wonder anymore that freebsd doesn't even try clearing
interrupts on A10, they enable/disable while masking/unmasking, not sure
yet about how linux does this, but i chose to use hwprios and response
register also, some hardcoded things still there to be cleaned..
so things seem to be working nicely, even after the userland freeze i
can see timers happily ticking away while blinking led, and they blink
it with some variance so i know there's code running.
decided to give statclock it's own timer&intr handler.
without userland, i don't feel motivated enough to begin working on any
of the missing drivers, so i think i'll have to take a break from
coding, diff some sources by eye, and think about how to deal with the
freeze, to take shortcuts fixing it or no not.
one way or another, i need to have userland working, patience is no
problem, but having the choice to try fixing it myself while knowing no
timeframe for the other solution and the possibility that this would
never get into OpenBSD anyway.. very tempting, almost too.
if not before, atleast when it's running long enough to allow logging
in, i will somehow put the srcs available for dload or something.
- Artturi
OpenBSD 5.3-current (GENERIC) #1: Fri Jul 5 11:57:30 EEST 2013
a...@tfort.local.lan:/usr/src/sys/arch/allwinner/compile/GENERIC
real mem = 1073741824 (1024MB)
avail mem = 1045819392 (997MB)
mainbus0 at root
cpu0 at mainbus0: ARM Cortex A8 R3 rev 2 (ARMv7 core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
aw0 at mainbus0: Cubieboard
awccm0 at aw0
awintc0 at aw0
awtimer0 at aw0: tick rate 187 KHz hz:100
awgpio0 at aw0
ehci0 at aw0
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Allwinner EHCI root hub" rev 2.00/1.00 addr 1
com0 at aw0: ns16550a, 16 byte fifo
com0: console
/dev/ksyms: Symbol table not valid.
umass0 at uhub0 port 1 configuration 1 interface 0 "Kingston
DataTraveler 2.0" rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <Kingston, DataTraveler 2.0, 6.00> SCSI2
0/direct removable serial.093065337B416393837F
sd0: 489MB, 512 bytes/sector, 1001472 sectors
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
boot device: sd0
root on sd0a (8718554ec688995c.a) swap on sd0b dump on sd0b
WARNING: CHECK AND RESET THE DATE!
init: copying out path `/sbin/init' 11
Automatic boot i
