On Sun, Jun 17, 2018 at 12:41:28PM +0200, Martin Husemann wrote:
> The kernel build makefiles do that. You typically get netbsd, netbsd.ub
> and netbsd.gz.ub as build result (on the architectures where you might
> need one of the latter)
As per https://wiki.netbsd.org/ports/evbarm/raspberry_pi/#in
On Sun, Jun 17, 2018 at 04:05:23PM +0530, Mayuresh wrote:
> On Sat, Jun 16, 2018 at 11:48:23PM +0200, Martin Husemann wrote:
> > We have tools to pack a kernel into such an image,
>
> I have started kernel recompilation by commenting out ulpt. Please share
> more information on tools to create ima
On Sat, Jun 16, 2018 at 11:48:23PM +0200, Martin Husemann wrote:
> We have tools to pack a kernel into such an image,
I have started kernel recompilation by commenting out ulpt. Please share
more information on tools to create image (or would make do that?).
Mayuresh
On Sat, 16 Jun 2018, Martin Husemann wrote:
A .ub file is an u-boot "bootm" image which contains the kernel.
We have tools to pack a kernel into such an image, but I don't know about
unpacking tools.
Strip off the first 64 bytes (Legacy U-boot image header) and you will be
left with netbsd.bi
On Sat, Jun 16, 2018 at 10:33:52PM +0530, Mayuresh wrote:
> On Sat, Jun 16, 2018 at 10:28:08PM +0530, Mayuresh wrote:
> >
> > Probably it's better to build kernel. But I am unclear about where to copy
> > the binary. See below.
>
> In /boot/boot.ini noticed netbsd-ODROID-C1.ub
A .ub file is an u
> You can probably check you kernel with
> config -x /kernel
D'oh -- "config -x /netbsd" or some such, of course.
Martin
> Just to try, created /boot.cfg as well as /boot/boot.cfg with
> userconf=disable ulpt*, but that had no effect.
The easiest way to check your system without some specific
driver is to interrupt the automatic boot process (by hitting
space), then boot with "boot -c", and issue the
disabl
On Sat, Jun 16, 2018 at 10:28:08PM +0530, Mayuresh wrote:
>
> Probably it's better to build kernel. But I am unclear about where to copy
> the binary. See below.
In /boot/boot.ini noticed netbsd-ODROID-C1.ub
But that results in:
# config -x /boot/netbsd-ODROID-C1.ub
config: /boot/netbsd-ODROID
On Sat, Jun 16, 2018 at 06:47:04PM +0200, Martin Neitzel wrote:
> For both the interactive or file-based tuning, you need to to
> have the userconf(4) option in your kernel. (It's GENERIC on
> i368/amd64 and most platforms, I don't know for sure about evbarm,
> though.)
As per evbarm/conf/GENERIC
On Sat, Jun 16, 2018 at 10:39:47AM +, m...@netbsd.org wrote:
> does drvctl -d ulpt0 work better?
> (with netbsd running)
never mind, that wno't work
does drvctl -d ulpt0 work better?
(with netbsd running)
On Sat, Jun 16, 2018 at 11:06:47AM +0530, Mayuresh wrote:
> But on above architecture I do not find boot.cfg. Instead I noticed
> cmdline.txt. Could not find much documentation on cmdline.txt though.
Just to try, created /boot.cfg as well as /boot/boot.cfg with
userconf=disable ulpt*, but that had
On device:
# uname -a
NetBSD pi 8.0_RC1 NetBSD 8.0_RC1 (RPI2.201804240813Z) evbarm
I wish to enable ugen interface, to use a USB scanner. The device is
getting detected as ulpt instead.
I checked the kernel conf, in which both ulpt and ugen are enabled. I
think disabling ulpt module would make i
13 matches
Mail list logo
