ating again, and stops, repeatedly.
Presumably a counter somewhere is wrapping round to zero instead of reaching
it's maximum value and stopping.
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
On Wed, Dec 16, 2015 at 02:47:10PM -0500, Ted Unangst wrote:
Tati Chevron wrote:
On Wed, Dec 16, 2015 at 11:13:36AM -0700, Theo de Raadt wrote:
>Your emails only contain opinions.
"Questions, comments, suggestions and any kind of help would also be
welcome".
Sorry if I mis-u
On Wed, Dec 16, 2015 at 11:13:36AM -0700, Theo de Raadt wrote:
Your emails only contain opinions.
"Questions, comments, suggestions and any kind of help would also be
welcome".
Sorry if I mis-understood the purpose of a mailing list.
--
Tati Chevron
Perl and FORTRAN specialis
On Wed, Dec 16, 2015 at 12:59:00PM -0500, Ted Unangst wrote:
Tati Chevron wrote:
But I don't see that touch-based devices are ever going to become the most
common devices to run OpenBSD, that's not realistic. Even ignoring servers and
headless devices, and only counting devices tha
On Wed, Dec 16, 2015 at 06:29:23PM +0100, Stefan Sperling wrote:
On Wed, Dec 16, 2015 at 05:10:45PM +, Tati Chevron wrote:
why does it have to be integrated into the same mouse driver that everybody
else uses?
Since you seem to care about this topic enough to actually contend
with what
On Wed, Dec 16, 2015 at 03:13:32PM +0100, Stefan Sperling wrote:
On Wed, Dec 16, 2015 at 12:55:03PM +, Tati Chevron wrote:
Sorry to be negative, but I just don't see the perceived value in this.
You wouldn't want to use OpenBSD on a trouchscreen computer if you
had one? Where w
On Wed, Dec 16, 2015 at 05:31:30PM +0100, Stefan Sperling wrote:
On Wed, Dec 16, 2015 at 04:11:21PM +, Tati Chevron wrote:
>So I believe this work is important.
I think it's much more important to look at the impact on existing use cases,
before making changes and introducing a lo
an that we gain anything
by copying that.
Sorry to be negative, but I just don't see the perceived value in this.
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
On Sat, Dec 05, 2015 at 07:33:11AM +0100, Stefan Kempf wrote:
Tati Chevron wrote:
This assembled and linked without problems on 5.7-release, but now when
I try it on 5.8-release, I get an error:
$ as -o charset.o charset.S
$ ld -Bstatic charset.o
ld: charset.o: relocation R_X86_64_32S
OpenBSD\0"
.long 0x00
.p2align 2
.section .data
bytestore: .quad 0x20
welcome: .ascii "Characterset generator by Tati Chevron, 27/4/2015."
.byte 0x0A
newline: .quad 0x0A
.section .text
.globl _start
_start:
mov $welcome, %rsi
mov $1, %rdi
mov $4, %rax
mov $53, %rdx
syscall
_loop:
pus
-fPIC
charset.o: could not read symbols: Bad value
What's changed?
charset.S is fairly trivial:
.section ".note", "a"
.p2align 2
.long 0x08
.long 0x04
.long 0x01
.ascii "OpenBSD\0"
.long 0x00
.p2align 2
.section .data
bytestore: .quad 0x20
welcome: .ascii "
n] [-p parallel] [-P pathlist] [-h hosts]
[-L logdir] [-l lockdir] [-b log] [-M threshold] [-X pathlist]
[pathlist ...]
Infact, trying to build other flavoured ports fails in a similar way.
What am I doing wrong here?
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and
On Sat, Nov 28, 2015 at 07:18:25PM +0100, Mark Kettenis wrote:
Date: Sat, 28 Nov 2015 17:12:03 +
From: Tati Chevron
cbb0 at pci1 dev 9 function 0 "ENE CB-1410 CardBus" rev 0x01: apic 1 int 22,
CardBus support disabled
cardslot0 at cbb0 slot 0 flags 0
pcmcia0 at cardslot0
- Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Capabilities: [a0] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Capabilities: [a0] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
ile support, and for Ted to write a new cut down
alternative version to go in base.
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
On Mon, Nov 09, 2015 at 08:23:08AM +, Nicholas Marriott wrote:
On Sun, Nov 08, 2015 at 09:01:52PM +, Tati Chevron wrote:
Is there any reason why the OpenBSD installer still defaults to a
terminal type of vt-220 for the VGA framebuffer console, and doesn't
even suggest pccon
27;ll look into that, and maintain a local patch here for X for the time
being.
Is there any reason why the OpenBSD installer still defaults to a terminal type
of vt-220 for the VGA framebuffer console, and doesn't even suggest pccon as an
alternative?
--
Tati Chevron
Perl and FORTRAN
F13-F24.
Either support the, 'real', sequences from a 122-key keyboard, or support the
shifted F1-F12 keys as F13-F24, or preferably, both.
Shall I make a diff to fix this?
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
kf23=\E[44~, kf24=\E[45~, khlp=, krdo=, use=xterm,
NetBSD consoles
#
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
6~,
+ kf15=\E[28~, kf16=\E[29~, kf17=\E[31~, kf18=\E[32~,
+ kf19=\E[33~, kf20=\E[34~, kf21=\E[42~, kf22=\E[43~,
+ kf23=\E[44~, kf24=\E[45~, khlp=, krdo=, use=xterm,
+
+
ANSI, UNIX CONSOLE, AND SPECIAL TYPES
#
# This section describes terminal classes and brands that are st
21 matches
Mail list logo
