Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 May 2010 20:44:17 +0200
From:      =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= <phcoder@gmail.com>
To:        freebsd-mips@freebsd.org
Subject:   GSoC Yeeloong port report: ddb
Message-ID:  <4BFD6C01.2020008@gmail.com>

next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5FDFBA2C299351E1C7FC9355

This is a multi-part message in MIME format.
--------------020108010401000607010702
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello, all. I would like announce progress on my GSoC of porting FreeBSD
to yeeloong. As you can see from minicom capture it already initialises
ddb before dereferencing NULL pointer in vm/vm_mmap.c. Loongson 2F
doesn't implement COP0 register indices so e.g. all cache information
will be hardcoded for now and received from bootloader in perspective.
I'm aware that many values in cpuinfo is still missing and that it will
create problems but at least I have debugger (even though debugger bugs
on mips64)

Available at:
http://bazaar.launchpad.net/~phcoder/kfreebsd-yeeloong/trunk/changes
Or
//depot/projects/soc2010/phcoder_yeeloong

Perforce copy will be outdated by about a day because I have trouble
with my option modem under FreeBSD and so I upload to perforce when I
have wifi access.

--=20
Regards
Vladimir '=CF=86-coder/phcoder' Serbinenko


--------------020108010401000607010702
Content-Type: application/cap;
 name="freebsd_ddb.cap"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="freebsd_ddb.cap"

Ym9vdAplbnRyeTogbWlwc19pbml0KCkKQ2FjaGUgaW5mbzoKICBwaWNhY2hlX3N0cmlkZSAg
ICA9IDAKICBwaWNhY2hlX2xvb3Bjb3VudCA9IDAKICBwZGNhY2hlX3N0cmlkZSAgICA9IDAK
ICBwZGNhY2hlX2xvb3Bjb3VudCA9IDAKY3B1MDogVW5rbm93biBjaWQgMCBwcm9jZXNzb3Ig
djMuOTkKICBNTVU6IFN0YW5kYXJkIEJBVCwgNjQgZW50cmllcwogIEwxIGktY2FjaGU6IDAg
d2F5cyBvZiAwIHNldHMsIDMyIGJ5dGVzIHBlciBsaW5lCiAgTDEgZC1jYWNoZTogMCB3YXlz
IG9mIDAgc2V0cywgMzIgYnl0ZXMgcGVyIGxpbmUKUGh5c2ljYWwgbWVtb3J5IGNodW5rKHMp
OgoweDQ1ZjAwMCAtIDB4ZmJhMWZmZiwgMjU5MjcyNzA0IGJ5dGVzICg2MzI5OSBwYWdlcykK
TWF4bWVtIGlzIDB4ZmJhMjAwMApLREI6IGRlYnVnZ2VyIGJhY2tlbmRzOiBkZGIKS0RCOiBj
dXJyZW50IGJhY2tlbmQ6IGRkYgpoej0xMDAgY3lsX3Blcl90aWNrOjQwMDAwMCBjeWxfcGVy
X3VzZWM6NDAwIGZyZXE6NDAwMDAwMDAwIGN5bF9wZXJfaHo6NDAwMDAwMCBjeWxfcGVyX3N0
YXRoejo0MDAwMDAwIGN5bF9wZXJfcHJvZmh6OjQwMDAwMDAKQ29weXJpZ2h0IChjKSAxOTky
LTIwMTAgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChjKSAxOTc5LCAxOTgwLCAx
OTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAxOTk0CglUaGUgUmVn
ZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmlnaHRzIHJlc2Vy
dmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1hcmsgb2YgVGhlIEZyZWVCU0Qg
Rm91bmRhdGlvbi4KRnJlZUJTRCA5LjAtQ1VSUkVOVCAjMjk6IFdlZCBNYXkgMjYgMTk6NTQ6
MTcgQ0VTVCAyMDEwCiAgICBwaGNvZGVyQGZyZWVic2QuYmc0NS5waG5ldDovaG9tZS9waGNv
ZGVyL2NvbXBpbGUvbWlwcy9ob21lL3BoY29kZXIvcDQveWVlbG9vbmcvc3JjL3N5cy9ZRUVM
T09ORyBtaXBzClRyYXAgY2F1c2UgPSAyIChUTEIgbWlzcyAobG9hZCBvciBpbnN0ci4gZmV0
Y2gpIC0ga2VybmVsIG1vZGUpClsgdGhyZWFkIHBpZCAwIHRpZCAwIF0KU3RvcHBlZCBhdCAg
ICAgIDB4ZmZmZmZmZmY4MDM4NWM2NDogICAgIGxidSAgICAgdjAsMjA1KGEwKQpkYj4g
--------------020108010401000607010702--

--------------enig5FDFBA2C299351E1C7FC9355
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iF4EAREKAAYFAkv9bA4ACgkQNak7dOguQgk5YAD9H2gmlX4yk8xZlfwuOAfwH97Q
1IxxmFEr5LCj1ISJHlEA/3N7bGUHH7ogWQ1G5xXksyJEjm7XBfC/wx/MvrUcbARF
=f1T7
-----END PGP SIGNATURE-----

--------------enig5FDFBA2C299351E1C7FC9355--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BFD6C01.2020008>