History log of /netbsd/sys/arch/evbmips/loongson/autoconf.c (Results 1 – 6 of 6)
Revision Date Author Comments
# 6c868ec6 10-Jan-2015 jmcneill <jmcneill@NetBSD.org>

if MEMORY_DISK_IS_ROOT is defined, dont try to guess the root device


# 1f8f5f2b 13-Mar-2013 macallan <macallan@NetBSD.org>

remove half-assed gdium-specific code in device_register and actually call
sys_platform->device_register()
how in Cthulhu's name did this ever work?


# 5f819ca3 27-Oct-2012 chs <chs@NetBSD.org>

split device_t/softc for all remaining drivers.
replace "struct device *" with "device_t".
use device_xname(), device_unit(), etc.


# 40637d6d 29-Jul-2012 mlelstv <mlelstv@NetBSD.org>

Do not call setroot() from MD code and from MI code, which has
unwanted sideeffects in the RB_ASKNAME case. This fixes PR/46732.

No longer wrap MD cpu_rootconf(), as hp300 port stores reboot informa

Do not call setroot() from MD code and from MI code, which has
unwanted sideeffects in the RB_ASKNAME case. This fixes PR/46732.

No longer wrap MD cpu_rootconf(), as hp300 port stores reboot information
as a side effect. Instead call MI rootconf() from MD code which makes
rootconf() now a wrapper to setroot().

Adjust several MD routines to set the global booted_device,booted_partition
variables instead of passing partial information to setroot().

Make cpu_rootconf(9) describe the calling order.

show more ...


# ee1607af 02-Mar-2012 nonaka <nonaka@NetBSD.org>

Added Lemote Yeeloong Notebook support.


# a1cb14f5 27-Aug-2011 bouyer <bouyer@NetBSD.org>

Add loongson support to evbmips, based on the OpenBSD loongson port
and the existing evbmips/gdium support.
This has been tested on a lemote fuloong device (boots multiuser),
should also support othe

Add loongson support to evbmips, based on the OpenBSD loongson port
and the existing evbmips/gdium support.
This has been tested on a lemote fuloong device (boots multiuser),
should also support other lemote devices (maybe with minor adjustments,
or adding missing drivers). There is some gdium support here too, but it
may not be yet complete (someone with a gdium would need to have a look,
hi macallan@ :)
loongson kernels are 64bits only: the loongson2f has ressources located
above the 2Gb physical address, and it's much easier to access it
using XKPHYS than trying to make it fit in the limited 32bit kernel
virtual space.

show more ...