Re: linking to git revisions in bugzilla

2021-05-07 Thread Oleksandr Tymoshenko
Yuri Pankov (yur...@freebsd.org) wrote: > Oleksandr Tymoshenko wrote: > > Kubilay Kocak (ko...@freebsd.org) wrote: > >> On 12/04/2021 9:02 am, Yuri Pankov wrote: > >>> While filing a bug, I noticed that the help only mentions svn revision > >>> numbe

Re: WSLg update on 1-5-2021 - BSD / WSL

2021-05-07 Thread Oleksandr Tymoshenko
David Chisnall (thera...@freebsd.org) wrote: > On 03/05/2021 22:37, Pete Wright via freebsd-current wrote: > > On 5/1/21 12:42 PM, Chargen wrote: > >> Dear all > >> > >> please note that I hope this message will be discussed to get this on the > >> roadmap for FreeBSD. Perhaps there is already talk

Re: linking to git revisions in bugzilla

2021-05-01 Thread Oleksandr Tymoshenko
Kubilay Kocak (ko...@freebsd.org) wrote: > On 12/04/2021 9:02 am, Yuri Pankov wrote: > > While filing a bug, I noticed that the help only mentions svn revision > > numbers, and "Preview" tab had no output when I tried putting "base > > ", so I'm wondering how do you link to git revisions? > > We

Re: geli broken in 13.0-BETA4 and later on armv8

2021-03-06 Thread Oleksandr Tymoshenko
Peter Jeremy via freebsd-current (freebsd-current@freebsd.org) wrote: > [Adding arm@ and making it clearer that this is armv8-only] > > On 2021-Mar-06 20:26:19 +1100, Peter Jeremy wrote: > >On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable > > wrote: > >>Somewhere between 13.0-ALPHA

Re: ThinkPad: reboots after successful shutdown -p

2019-11-18 Thread Oleksandr Tymoshenko
Bjoern A. Zeeb (bzeeb-li...@lists.zabbadoz.net) wrote: > On 18 Nov 2019, at 7:14, Xin Li wrote: > > > Hi, > > > > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the > > system would shut down and seemingly powered off, then it would > > restart > > after about 5-10 seconds. > > I

Re: What is evdev and autoloading?

2019-02-19 Thread Oleksandr Tymoshenko
Michael Gmelin (gre...@freebsd.org) wrote: > > > > On 18. Feb 2019, at 23:54, Mark Linimon wrote: > > > >> On Mon, Feb 18, 2019 at 08:50:27AM -0800, Rodney W. Grimes wrote: > >> I think one serious problem here is the summary dismissal of things > >> simply on the "5 year old" basis. > > > > I

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Oleksandr Tymoshenko
Bernd Walter (ti...@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote: > > Bernd Walter (ti...@cicely7.cicely.de) wrote: > > > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > > > Bernd Walter (

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Oleksandr Tymoshenko
Bernd Walter (ti...@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote: > > Bernd Walter (ti...@cicely7.cicely.de) wrote: > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > > > https://github.com/gonz

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Oleksandr Tymoshenko
Bernd Walter (ti...@cicely7.cicely.de) wrote: > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote: > https://github.com/gonzoua/evdev-dump/tree/freebsd > ... > checking for unistd.h... yes > checking linux/input.h usability... no > checking linux/input.h presence... no > checking for lin

Re: INTRNG

2018-02-23 Thread Oleksandr Tymoshenko
Jon Brawn (j...@brawn.org) wrote: > Wotcha Gang! > > In my travels through the arm64 GENERIC config file I came across the option > ‘INTRNG’, and wondered what it was: > > INTeRrupt Next Generation? > INTeger Random Number Generator? > IN TRaiNinG? > INTerrupt Random Number Generator? > INdepend

Re: I2C trackpad

2018-02-08 Thread Oleksandr Tymoshenko
Ian FREISLICH (ian.freisl...@capeaugusta.com) wrote: > Hey, > > I recently acquired a new laptop (Asus UX490U) which for the most part > works with current except that: > > 1. Sound output doesn't work. > 2. The trackpad doesn't work. > > I'm not bothered about sound and I haven't investigated t

Re: SVN r327444 breaks current build

2018-01-01 Thread Oleksandr Tymoshenko
Ian Lepore (i...@freebsd.org) wrote: > On Sun, 2017-12-31 at 15:53 -0800, Oleksandr Tymoshenko wrote: > > Nathan Whitehorn (nwhiteh...@freebsd.org) wrote: > > > > > > > > > > > > On 12/31/17 14:22, Oleksandr Tymoshenko wrote: > > > > &

Re: SVN r327444 breaks current build

2017-12-31 Thread Oleksandr Tymoshenko
Nathan Whitehorn (nwhiteh...@freebsd.org) wrote: > > > On 12/31/17 14:22, Oleksandr Tymoshenko wrote: > > Michael Butler (i...@protected-networks.net) wrote: > >> Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o > >> --- vt_termcolors.o --

Re: SVN r327444 breaks current build

2017-12-31 Thread Oleksandr Tymoshenko
Michael Butler (i...@protected-networks.net) wrote: > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vt_font_default.o > --- vt_termcolors.o --- > /usr/src/sys/dev/vt/colors/vt_termcolors.c:158:55: error: too many > arguments to function call, expected 4, have 5 > if (vt_par

Re: panic: invalid bcd xxx

2017-03-08 Thread Oleksandr Tymoshenko
Eric van Gyzen (vangy...@freebsd.org) wrote: > On 03/04/2017 11:44, Oleksandr Tymoshenko wrote: > > Adrian Chadd (adrian.ch...@gmail.com) wrote: > >> We're not; we need to cope with crappy BIOS emulations and not crash :) > >> > >> What's Linux doing

Re: panic: invalid bcd xxx

2017-03-04 Thread Oleksandr Tymoshenko
Adrian Chadd (adrian.ch...@gmail.com) wrote: > On 2 March 2017 at 01:31, Matthias Apitz wrote: > > On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin > > wrote: > >> > >> > >> > >>> On 2 Mar 2017, at 00:35, Adrian Chadd wrote: > >>> > >>> This is an emulated BIOS though, right? > >>> > >>> I

Re: basic evdev setup

2017-02-15 Thread Oleksandr Tymoshenko
Andriy Gapon (a...@freebsd.org) wrote: > > Oleksandr, > > at the moment the documentation for evdev on FreeBSD is very scarce, even if > we > talk about wiki pages, informal howto-s or blog posts. > So, I would like to ask your help for a very basic evdev test setup. > > All input devices I hav

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

2017-02-10 Thread Oleksandr Tymoshenko
Toomas Soome (tso...@me.com) wrote: > > >> > >> From reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks like > >> names are in the form of typeN:M, where type is interface type, > >> N is disk id and M is partition id. So 3 disks in my setup > >> may be mmc0, mmc0:1, mmc0:2. > >> > >>

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

2017-02-09 Thread Oleksandr Tymoshenko
Toomas Soome (tso...@me.com) wrote: > > > On 9. veebr 2017, at 17:05, Karl Denninger wrote: > > > > > > On 2/9/2017 08:58, Toomas Soome wrote: > >>> On 9. veebr 2017, at 16:36, Karl Denninger > >>> wrote: > >>> > >>> > >>> On 2/8/2017 16:18, Karl Denninger wrote:

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

2017-02-09 Thread Oleksandr Tymoshenko
Toomas Soome (tso...@me.com) wrote: > > > On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko wrote: > > > > Toomas Soome (tso...@me.com) wrote: > >> > >>> On 9. veebr 2017, at 17:05, Karl Denninger wrote: > >>> > >>> > >&

Re: evdev no /dev/input FreeBSD 12.0-CURRENT #0 r311461

2017-01-11 Thread Oleksandr Tymoshenko
Jesper Schmitz Mouridsen (jesper@schmitz.computer) wrote: > Hello. > > I'm new to using current and to posting here. > I've a old spare T60 1951-FEG wiith Intel Graphics Media Accelerator 950 > (info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0). > Intel Core 2 Duo (Merom) T5600.

Re: evdev patches

2016-08-05 Thread Oleksandr Tymoshenko
> On Aug 5, 2016, at 12:26 PM, Lundberg, Johannes > wrote: > > ​Hi > > The evdev patched kernel found here > https://wiki.freebsd.org/SummerOfCode2014/evdev_Touchscreens > is over a year old and does not patch cleanly to current. > > Does anyone have a set of patches for evdev that will apply

Re: Dwarf problem with gcc and gdb

2015-12-08 Thread Oleksandr Tymoshenko
> On Dec 8, 2015, at 10:42 AM, John Baldwin wrote: > > On Tuesday, December 08, 2015 12:31:11 PM David Chisnall wrote: >> The gdb in the base system doesn’t support DWARF4. Use gdb791 or lldb-devel >> from ports (I believe gdb791 is probably a better bet on ARM, currently). > > gdb710 in port

Re: am335x-bone.dts not exist

2015-05-24 Thread Oleksandr Tymoshenko
> On May 24, 2015, at 12:12 AM, Garrett Cooper wrote: > > On May 24, 2015, at 0:07, Oleksandr Tymoshenko wrote: > >>> On May 23, 2015, at 7:21 PM, Andrey Fesenko wrote: >>> >>> # uname -a >>> FreeBSD des.local 11.0-CURRENT FreeBSD 11.0-CURR

Re: am335x-bone.dts not exist

2015-05-24 Thread Oleksandr Tymoshenko
> On May 23, 2015, at 7:21 PM, Andrey Fesenko wrote: > > # uname -a > FreeBSD des.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r283306: Sat > May 23 11:56:46 MSK 2015 > root@des.local:/usr/obj/usr/src/sys/GENERIC amd64 > > I'm build BEAGLEBONE with crochet. > > build error > > Mounting UFS par

Re: FreeBSD/armv6z/clang on Raspberry Pi 512MB (with U-Boot + ubldr)

2012-12-12 Thread Oleksandr Tymoshenko
On 12/12/2012 9:08 AM, Daisuke Aoyama wrote: Hi, I've created FreeBSD clang world for RPI based on svn 244112 + eabi.diff(NOT USE) + few NetBSD code. I didn't test with "-mfloat-abi=softfp" but it might work. The first version is released at my Japanese blog: http://shell.peach.ne.jp/aoyama/a

Re: : jemalloc_arena.c:182: Failed assertion: "p[i] == 0"

2012-04-30 Thread Oleksandr Tymoshenko
On 30/04/2012 1:52 PM, Pedro Giffuni wrote: On 04/30/12 14:04, Oleksandr Tymoshenko wrote: On 29/04/2012 12:04 PM, Adrian Chadd wrote: .. and the output from the buildworld: .. skipped .. -DSOFTFLOAT_FOR_GCC -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -Wsystem-headers -Werror -Wall

Re: : jemalloc_arena.c:182: Failed assertion: "p[i] == 0"

2012-04-30 Thread Oleksandr Tymoshenko
On 29/04/2012 12:04 PM, Adrian Chadd wrote: .. and the output from the buildworld: .. skipped .. -DSOFTFLOAT_FOR_GCC -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c jemalloc_jemalloc.c -o jemalloc_jemalloc

Re: Status on X220

2012-04-20 Thread Oleksandr Tymoshenko
On 19/04/2012 8:17 PM, Kevin Oberman wrote: > I made a quick attempt at the card reader, but had no luck finding a > driver that would work. Still, the system has worked for me for at > least 6 months, now. It seems the driver you need is sdhci (alogn with mmc and mmcsd). X220 card reader suppo

Re: DTrace on FreeBSD

2012-04-18 Thread Oleksandr Tymoshenko
On 17/04/2012 12:11 PM, Adrian Chadd wrote: On 17 April 2012 01:44, Sevan / Venture37 wrote: A part (the simple one) of the code has been reviewed. Anyone interested in getting KDTRACE_HOOKS enabled by default is free to do an independent review and post it here. Adam Leventhal on KDTRACE_H

Re: [head tinderbox] failure on mips/mips

2012-03-27 Thread Oleksandr Tymoshenko
On 2012-03-27, at 11:14 AM, John Baldwin wrote: > /obj/mips.mipsel/src/kerberos5/libexec/kimpersonate/../../lib/libvers/libvers.a >> /obj/mips.mipsel/src/tmp/usr/bin/ld: > /obj/mips.mipsel/src/tmp/usr/lib/libkafs5.so symbol number 13 references > nonexistent SHT_SYMTAB_SHNDX section >> /obj/mi

Re: DTrace/MIPS port

2012-03-26 Thread Oleksandr Tymoshenko
On 01/03/2012 1:49 PM, Oleksandr Tymoshenko wrote: Hello, Last few weeks I've been working on DTrace port for MIPS architecture. I believe that project reached the stage when it's ready for public review/testing before going into the tree. Patch and some information could be found

DTrace/MIPS port

2012-03-01 Thread Oleksandr Tymoshenko
Hello, Last few weeks I've been working on DTrace port for MIPS architecture. I believe that project reached the stage when it's ready for public review/testing before going into the tree. Patch and some information could be found here: http://people.freebsd.org/~gonzo/mips/dtrace/ I'd apprecia

Re: add 'ldd' to cross-tools ?

2012-01-04 Thread Oleksandr Tymoshenko
On 04/01/2012 2:23 PM, Luigi Rizzo wrote: Hi, in doing cross-builds of picobsd, i found i need a cross-version of "ldd" so i can run it on the host to detect which shared libraries are used by binaries on the target architecture (for amd64->i386 there is a partial workaround, but don't know if it