Re: Cross-compiling Haiku from NetBSD?

2018-12-03 Thread Thomas Mueller
> On Mon 03 Dec 2018 at 07:59:55 +, Thomas Mueller wrote:
> > You mention Haiku.  Did you ever attempt to cross-compile Haiku from
> > NetBSD? 
>   
> > I tried but never succeeded, apparently because Haiku build system
> > makes assumptions about where certain files are located on host
> > system.  Some of these differ for NetBSD and even FreeBSD. 

> Speaking of Haiku: I was just wondering if the display server and the
> userland graphics libraries are sufficently stand-alone that one could
> run them under NetBSD? It would make a nice replacement for X and
> Wayland and GTK... 

> Tom
> -Olaf.  
  
> ___ Olaf 'Rhialto' Seibert  

I once asked on haiku-development emailing list if it would be possible to port 
Web Positive browser to Linux and BSD, and the answer was that it would be 
difficult to impossible because of differences and incompatibilities between 
the Haiku software libraries and the software libraries in Linux and *BSD.

So I imagine it would be practically impossible to port Haiku display server to 
Linux or BSD.  But I don't know everything, could possibly be wrong on this 
issue.

Tom



daily CVS update output

2018-12-03 Thread NetBSD source update


Updating src tree:
P src/bin/sh/alias.c
P src/bin/sh/alias.h
P src/bin/sh/eval.c
P src/bin/sh/eval.h
P src/bin/sh/expand.c
P src/bin/sh/input.c
P src/bin/sh/main.c
P src/bin/sh/parser.c
P src/bin/sh/parser.h
P src/bin/sh/sh.1
P src/bin/sh/syntax.c
P src/bin/sh/syntax.h
P src/bin/sh/trap.c
P src/bin/sh/trap.h
P src/bin/sh/var.c
P src/bin/sh/var.h
P src/libexec/httpd/CHANGES
P src/libexec/httpd/bozohttpd.8
P src/libexec/httpd/bozohttpd.c
P src/libexec/httpd/dir-index-bozo.c
P src/share/man/man4/mpii.4
P src/share/mk/bsd.own.mk
P src/sys/arch/x86/isa/isa_machdep.c
P src/sys/arch/x86/x86/efi.c
P src/sys/dev/acpi/acpi_mcfg.c
P src/sys/dev/ic/ahcisatareg.h
P src/sys/dev/pci/mfii.c
P src/sys/dev/pci/mpii.c
P src/sys/dev/pci/mpiireg.h
P src/sys/dev/pci/pcidevs
P src/sys/dev/pci/pcidevs.h
P src/sys/dev/pci/pcidevs_data.h
P src/sys/dev/pci/ixgbe/ixgbe.c
P src/sys/dev/pci/ixgbe/ixgbe.h
P src/sys/dev/usb/if_mue.c
P src/sys/kern/sys_socket.c
P src/usr.bin/pkill/pkill.1

Updating xsrc tree:


Killing core files:




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  52439284 Dec  4 03:03 ls-lRA.gz


Re: current - latest suspend tests T43 - T30 - R51

2018-12-03 Thread maya
On Tue, Dec 04, 2018 at 12:26:53AM +0100, Riccardo Mottola wrote:
> Further question: if I see "Flushing disk caches" but still I get a dirty
> file system when I reboot on the T30 and R51  - why?

The dirty filesystem thing is a nice trick: if you mount rw it will
mark a bit as 'dirty', and if it unmounts, it'll clear the bit.

Then if anything other than proper, clean shutdown happens (where
unmount will happen) it knows it should fsck.


current - latest suspend tests T43 - T30 - R51

2018-12-03 Thread Riccardo Mottola

Hi,

given the recent commits I got the netbsd-GENERIC.gz kernel from releng 
as of 3 Dec.


ThinkPad T43
Nothing disabled. "Reference" but still not perfect sleep:

- goes correctly to sleep
- comes up again
- with bge0 working
	- TouchPad and TrackPoint are not working after resume (even if sleep 
was put without running X11 and starting it later)
- with iwi0 configured, went to sleep, but did not resume correctly, 
remaining a black screen and unresponsive system (fan whirring)



ThinkPad T30
Disable:
audio, video, isa, usb, fxp, iwi

I still get a reboot of fatal protection fault in supervisor mode, 
trap_tss() at netbsd:trap_tss


If desired I can attach a screenshot.

ThinkPad R51
Disable:
audio, video, isa, usb, fxp, iwi

I see 2 green lines of kernel messages and then a black screen, however 
the laptop does not reboot nor is off. I need to power-cycle it.



Essentially, since last attempts, nothing changed.

Given the dmesg attached for T50 and , what else could I disable?
I'm out of ideas!

Further question: if I see "Flushing disk caches" but still I get a 
dirty file system when I reboot on the T30 and R51  - why?


Riccardo
[   1.000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 
2004, 2005,
[   1.000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 
2016, 2017,
[   1.000] 2018 The NetBSD Foundation, Inc.  All rights reserved.
[   1.000] Copyright (c) 1982, 1986, 1989, 1991, 1993
[   1.000] The Regents of the University of California.  All rights 
reserved.

[   1.000] NetBSD 8.99.26 (GENERIC) #0: Mon Dec  3 06:43:19 UTC 2018
[   1.000]  
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
[   1.000] total memory = 2038 MB
[   1.000] avail memory = 1983 MB
[   1.000] timecounter: Timecounters tick every 10.000 msec
[   1.000] Kernelized RAIDframe activated
[   1.000] running cgd selftest aes-xts-256 aes-xts-512 done
[   1.000] userconf: configure system autoconfiguration:
[   1.000] uc> disable audio
[   1.000] [  0] audio* disabled
[   1.000] [  1] audio* disabled
[   1.000] uc> i^H ^Hdisable video
[   1.000] [  6] video* disabled
[   1.000] uc> disable isa
[   1.000] [469] isa0 disabled
[   1.000] [470] isa0 disabled
[   1.000] [471] isa0 disabled
[   1.000] [472] isa0 disabled
[   1.000] [473] isa0 disabled
[   1.000] [474] isa0 disabled
[   1.000] [475] isa0 disabled
[   1.000] [476] isa0 disabled
[   1.000] uc> i^H ^Hdisable usb
[   1.000] [542] usb* disabled
[   1.000] [543] usb* disabled
[   1.000] [544] usb* disabled
[   1.000] [545] usb* disabled
[   1.000] [546] usb* disabled
[   1.000] [547] usb* disabled
[   1.000] uc> disable fxp
[   1.000] [156] fxp* disabled
[   1.000] [157] fxp* disabled
[   1.000] uc> disable iwi
[   1.000] [418] iwi* disabled
[   1.000] uc> quit
[   1.000] Continuing...
[   1.000] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
[   1.030] IBM 288732G (ThinkPad R51)
[   1.030] mainbus0 (root)
[   1.030] ACPI: RSDP 0x000F6DA0 24 (v02 IBM   )
[   1.030] ACPI: XSDT 0x7F6EB16B 4C (v01 IBMTP-1V
1290  LTP )
[   1.030] ACPI: FACP 0x7F6EB200 F4 (v03 IBMTP-1V
1290 IBM  0001)
[   1.030] Firmware Warning (ACPI): 32/64X length mismatch in 
FADT/Gpe0Block: 64/32 (20180810/tbfadt-642)
[   1.030] Firmware Warning (ACPI): Optional FADT field Gpe1Block has valid 
Address but zero Length: 0x102C/0x0 (20180810/tbfadt-693)
[   1.030] ACPI: DSDT 0x7F6EB3E7 00BA37 (v01 IBMTP-1V
1290 MSFT 010E)
[   1.030] ACPI: FACS 0x7F6F8000 40
[   1.030] ACPI: SSDT 0x7F6EB3B4 33 (v01 IBMTP-1V
1290 MSFT 010E)
[   1.030] ACPI: ECDT 0x7F6F6E1E 52 (v01 IBMTP-1V
1290 IBM  0001)
[   1.030] ACPI: TCPA 0x7F6F6E70 32 (v01 IBMTP-1V
1290 PTL  0001)
[   1.030] ACPI: BOOT 0x7F6F6FD8 28 (v01 IBMTP-1V
1290  LTP 0001)
[   1.030] ACPI: 2 ACPI AML tables successfully acquired and loaded
[   1.030] cpu0 at mainbus0
[   1.030] cpu0: Intel(R) Pentium(R) M processor 1500MHz, id 0x695
[   1.030] cpu0: package 0, core 0, smt 0
[   1.030] acpi0 at mainbus0: Intel ACPICA 20180810
[   1.030] acpi0: X/RSDT: OemId , AslId < 
LTP,>
[   1.030] acpiecdt0 at acpi0: ACPI Embedded Controller via ECDT
[   1.030] LNKA: ACPI: Found matching pin for 0.2.INTA at func 0: 11
[   1.030] LNKA: ACPI: Found matching pin for 0.29.INTA at func 0: 11
[   1.030] LNKD: ACPI: Found matching pin for 0.29.INTB at func 1: 11
[   1.030] LNKC: ACPI: Found matching pin for 0.29.INTC at func 2: 11
[   1.030] LNKH: ACPI: Found matching pin for 0.29.INTD at func 7: 11
[   

Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-03 Thread Mike Pumford




On 03/12/2018 22:47, Manuel Bouyer wrote:

Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't test).

Just updating my current tree and doing a build. Will then take a USB 
bootable image to work and test it with the SAS3 HBA there.


Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-03 Thread Manuel Bouyer
Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't test).

I plan to get this in netbsd-8 along with the mfii driver (and my if_bge
improvements).

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: Cross-compiling Haiku from NetBSD?

2018-12-03 Thread Rhialto
On Mon 03 Dec 2018 at 07:59:55 +, Thomas Mueller wrote:
> You mention Haiku.  Did you ever attempt to cross-compile Haiku from
> NetBSD?
> 
> I tried but never succeeded, apparently because Haiku build system
> makes assumptions about where certain files are located on host
> system.  Some of these differ for NetBSD and even FreeBSD.

Speaking of Haiku: I was just wondering if the display server and the
userland graphics libraries are sufficently stand-alone that one could
run them under NetBSD? It would make a nice replacement for X and
Wayland and GTK...

> Tom
-Olaf.
-- 
___ Olaf 'Rhialto' Seibert  -- "What good is a Ring of Power
\X/ rhialto/at/falu.nl  -- if you're unable...to Speak." - Agent Elrond


signature.asc
Description: PGP signature


Re: issues with touchpad after update

2018-12-03 Thread Brett Lymn
On Sun, Dec 02, 2018 at 01:21:11PM +0100, Riccardo Mottola wrote:
> 
> I don't have any (yet) settings in sysctl . Mine wopere 12 and 5:
> 

That means you don't have the latest synaptics driver, I updated the
default values after feedback from Martin.

> 
> using your values, I can use the touchpad "normally", that is, with only 
> one finger it does the job, which is already something :)

Good.

> Scrolling however is almost unusable, very jerky, speeds up and moves 
> around, but really "happens" only when I put two fingers on it.
> 

It should only happen when you put two fingers on the touchpad.  If you
are seeing cursor movements when you have two fingers on the touchpad
then you need to increase:

hw.synaptics.finger_scroll-hysteresis

but you need the latest synaptics code to do that due to a bug that
prevented you setting the value in the older version.  This stops the
driver flicking between two finger scroll and cursor movement randomly -
the higher the value the longer it stays in scroll mode.

> Reading the values, the one I had as "min" should however be fine, since 
> it is the minimum width and I have pretty large fingers, they will be 
> never close together.
> 

I have pretty large fingers too - I think the difference is how the
touchpad reports fingers.  On my touchpad I don't get a width reported
for a finger, it just gives me a special width value that says one
finger is on the touchpad.  I do have a later version of firmware on my
touchpad though.

> 
> 
> in dmesg I see:
> 
> [ 1.020391] pms0 at pckbc1 (aux slot)
> [ 1.020391] pms0: Synaptics touchpad version 7.4
> [ 1.020391] pms0: Extended W mode, Palm detect, Multi-finger Report
> 

Mine is:

[ 1.160334] pms0 at pckbc1 (aux slot)
[ 1.160334] pms0: Synaptics touchpad version 8.1
[ 1.160334] pms0: Extended W mode, Passthrough, Palm detect, One button 
click pad, Multi-finger Report, Multi-finger

> I am actually unsure my touchpad is Multi-finger! I don't think, it has 
> a "scroll area" on the right (which never worked on NetBSD, only on Windows)
> 

The capabilities you see are decoded from queries made to the touchpad.
On initialisation the driver asks the touchpad what it is capable of,
what you see in dmesg is what the touchpad says it can do.

> Given the above test, it indeed appears to be multi-touch! But not 
> usable... the Scroll bar at right was probably something specific to the 
> windows driver (I don't have windows anymore... I used the other 
> partition to test Haiku) [1]
> 

I don't have a scollbar so I cannot test that but I am thinking that I
need to rework the handling of the two finger scroll, it is very
sensitive - I am thinking I should change the scaling on it to be a
divisor instead of a multiplier so that large movements don't produce
too many scroll events - the X server really doesn't like lots of scroll
events.

-- 
Brett Lymn
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"


Cross-compiling Haiku from NetBSD?

2018-12-03 Thread Thomas Mueller
Excerpt from Riccardo Mottola, Subject: Re: issues with touchpad after update:

> Given the above test, it indeed appears to be multi-touch! But not usable...  
> the Scroll bar at right was probably something specific to the windows driver 
> (I don't have windows anymore... I used the other partition to test Haiku) [1]

> Riccardo

> [1] : OffTopic : I always wanted some NetBSD (and FreeBSD, OpenBSD, Linux)
> stickers to replace the "Window 7" logo ... possibly with the Daemon and/or
> the old logo, Only the new Flag and text is a bit anonymous

You mention Haiku.  Did you ever attempt to cross-compile Haiku from NetBSD?

I tried but never succeeded, apparently because Haiku build system makes 
assumptions about where certain files are located on host system.  Some of 
these differ for NetBSD and even FreeBSD.

I changed the subject so as not to be accused of thread hijacking.

Anybody who is interested can respond on this list or on haiku-development 
list, if they are subscribed to that list, as I am.

Tom