I think this is a bug in your device tree because the KASSERT was
intentional:
- In the ACPI case, we probe for CPU PMU support before calling
armv8_pmu_init.
- In the FDT case, the PMU attaches to a node described in the device
tree.
So if you hit this KASSERT, AFAICT it means your
The script no longer works:
Starting devpubd.
/libexec/devpubd-hooks/02-wedgenames: 164: Syntax error: end of file unexpected
(expecting "done")
Take care,
Jared
On Thu, 5 Aug 2021, Robert Elz wrote:
Module Name:src
Committed By: kre
Date: Thu Aug 5 12:52:47 UTC 2021
ias Nygren wrote:
>
> On Fri, 30 Jul 2021 22:36:45 +0200
> Tobias Nygren wrote:
>
>> On Fri, 30 Jul 2021 17:25:46 -0300 (ADT)
>> Jared McNeill wrote:
>>
>>> Why only A20?
>>
>> It is the hardware I have on hand. If you know specifically which
&g
Why only A20?
On Fri, 30 Jul 2021, Tobias Nygren wrote:
Module Name:src
Committed By: tnn
Date: Fri Jul 30 12:46:46 UTC 2021
Modified Files:
src/sys/arch/arm/sunxi: sunxi_platform.c
src/sys/dev/ic: com.c
Log Message:
com(4): fix FIFO for DW_APB on Allwinner
Building tools on macOS:
/Users/jmcneill/netbsd/git-src/tools/compat/../../lib/libc/regex/regcomp.c:1585:8:
error: implicit declaration of function 'reallocarray' is invalid
in C99 [-Werror,-Wimplicit-function-declaration]
ncs = reallocarray(p->g->sets, p->g->ncsets + 1,
On Mon, 22 Feb 2021, Ryo Shimizu wrote:
I think this condition is not necessary since cpu_idle() is just called from
idle_loop(),
and ci_intr_depth is always zero at this time.
Ah yes, my mistake! Please feel free to revert this commit as part of
your proposed change.
I noticed this on reboot since this change:
[ 3636.2891122] turning off swap...stopping swap on /swap failed with error 16
[ 3636.2991109] stopping swap on /swap2 failed with error 16
Can you have a look?
Thanks!
Jared
On Tue, 16 Feb 2021, Juergen Hannken-Illjes wrote:
Module Name:
I forgot that I added dma-ranges support back in Feb last year. All good,
please ignore me :)
On Thu, 21 Jan 2021, Jared McNeill wrote:
This driver is not 64-bit safe and should not be enabled on aarch64 as-is. I
think before turning it on we should restrict it to the lower 1GB of memory
This driver is not 64-bit safe and should not be enabled on aarch64 as-is.
I think before turning it on we should restrict it to the lower 1GB of
memory like the Pi3 models where we know it at least has a chance of
working. You can do this easily by creating a restrictive tag using
The change isn't wrong, but I booted the wrong kernel and it does not fix
the aarch64 issue I am seeing.
On Sun, 17 Jan 2021, Jared D. McNeill wrote:
Module Name:src
Committed By: jmcneill
Date: Sun Jan 17 15:13:15 UTC 2021
Modified Files:
src/sys/dev/wscons:
Not sure if it is this exact change, but I am no longer able to build
tools on Ubuntu 20.04.1:
--- lint1 ---
# link lint1/lint1
cc -O -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-I/home/jmcneill/netbsd/cvs-src/obj/tooldir.Linux-5.8.0-34-generic-x86_64/include/compat
Hi!
sys/external/gpl2/dts/dist is meant for upstream dts files only. Do
you mind moving this to sys/arch/arm/dts with the other custom dts files?
Thanks!
Jared
On Fri, 1 Jan 2021, Ryo Shimizu wrote:
Module Name:src
Committed By: ryo
Date: Fri Jan 1 07:41:46 UTC 2021
Oops. The change was to make sure that a devicetree node with a
"rockchip,grf" property on a device type that doesn't provide a config
struct doesn't deref a NULL ptr.
On Fri, 1 Jan 2021, Jared D. McNeill wrote:
Module Name:src
Committed By: jmcneill
Date: Fri Jan 1 11:44:41
I think WSFB_VRAM_IS_RAM is meant to be a hint for what kind of memory you
get when you mmap the device. When shadow FB is used, that is generally
only used for rasops and mmap bypasses the shadow and uses device memory
directly. So I think this could cause performance regressions on such
On Sat, 12 Sep 2020, Olaf Seibert wrote:
bozohttpd: add .m4a and .m4v file extensions.
I don't think audio/mpeg is correct for .m4a. Since .m4a is MPEG audio in
an MP4 container, I would follow RFC 4337 ("MIME Type Registration for
MPEG-4") here which says you should use audio/mp4 instead.
This causes issues with the source tree on case insensitive file-systems :(
On Wed, 22 Jul 2020, Martin Husemann wrote:
Module Name:src
Committed By: martin
Date: Wed Jul 22 16:50:41 UTC 2020
Modified Files:
src/distrib/sets/lists/etc: mi
src/etc: rc
On Sun, 2 Aug 2020, Roland Illig wrote:
Module Name:src
Committed By: rillig
Date: Sun Aug 2 09:43:22 UTC 2020
Modified Files:
src/usr.bin/make: var.c
Log Message:
make(1): use shorter local variable names
The c in cp was redundant since the context makes it obvious
I think this will have issues on some big.LITTLE configurations
like Rockchip RK3399.
In the RK3399 case cpu[0-3] is VIPT I$ and cpu[4-5] is PIPT I$. Boot
order of secondaries is not guaranteed so it is possible to get different
values of aarch64_cache_vindexsize from one boot to the next.
On Fri, 29 May 2020, Izumi Tsutsui wrote:
src/distrib/common/bootimage/Makefile.bootimage (included from
Makefile.installimage) already has "USE_MBR?= no" line.
Makefile.installimage refers to it before including Makefile.bootimage and
this test was causing make to throw an error:
Unfortunately this breaks building on a 9.0 arm64 host because it is
picking up /usr/include/aarch64/armreg.h and the one in 9.0 is missing a
bunch of stuff. It works when using armreg.h from the source tree instead,
eg:
-#include
+#include "/path/to/src/sys/arch/aarch64/include/armreg.h"
Great work! One small remark:
+static int
+ave_fdt_match(device_t parent, cfdata_t cf, void *aux)
+{
+ static const char * compatible[] = {
+#ifdef _LP64
+ "socionext,unifier-ld20-ave4",
+#else
+
Hi --
Is there really a need for all of this fdt stuff for SCA2A11? I would
expect that the board can be fully supported in ACPI mode.
Thanks,
Jared
On Wed, 18 Mar 2020, Tohru Nishimura wrote:
Module Name:src
Committed By: nisimura
Date: Wed Mar 18 08:49:51 UTC 2020
On Nov 27, 2019, at 9:08 PM, Jason R Thorpe wrote:
>
> + firqh = kmem_alloc(sizeof(*firqh), KM_SLEEP);
> + firqh->ih_irq = firq;
> + firqh->ih_fn = func;
> + firqh->ih_arg = arg;
> + TAILQ_INSERT_TAIL(>intr_handlers, firqh, ih_next);
> +
> + return firqh;
I should have
On Fri, 26 Jul 2019, Rin Okuyama wrote:
Also, convert loop of byte-wise copy into memset.
I am a bit concerned about this change because IIRC there are platforms
where memset etc. cannot be used on device memory.
;
argument. ;)
On Tue, Jul 23, 2019 at 12:25:16PM -0300, Jared McNeill wrote:
Hi Thomas --
The bcm43xx firmware is different from other firmware images because it is
not loaded by the kernel directly. The tool that loads this image lives in
/usr/sbin, so /usr/libdata/firmware seemed more a
Hi Thomas --
The bcm43xx firmware is different from other firmware images because it is
not loaded by the kernel directly. The tool that loads this image lives in
/usr/sbin, so /usr/libdata/firmware seemed more appropriate. The path
already existed in the list of firmware search paths (sysctl
You are correct, my mistake!
On Tue, 21 May 2019, Tetsuya Isaki wrote:
At Thu, 9 May 2019 10:28:19 -0300 (ADT),
Jared McNeill wrote:
With order of operations here, and track->volume being in range 0...256, I
don't think this will work anyway. volume of 255 of less will cause the
sam
With order of operations here, and track->volume being in range 0...256, I
don't think this will work anyway. volume of 255 of less will cause the
sample to be 0, and 256 the original value.
On Wed, 8 May 2019, m...@netbsd.org wrote:
Is there some scenario where this made a difference?
it
Because we are using image type "kernel_noload" instead of "kernel" for
GENERIC. The header on "kernel" type images contains a load address, and
U-Boot will uncompress the kernel there. For "kernel_noload" type images
there is no load address specified, with the expectation that the kernel
On Sat, 1 Dec 2018, Martin Husemann wrote:
Would it be possible (grep in dmesg, check sysctl, whatever?) to verify
we are running on an EC2?
And if not, require some explicit rc.conf entry to force this (e.g. for
testing puroses), but in usual setups default this script to off?
Exactly what
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
On Sat, 1 Dec 2018, m...@netbsd.org wrote:
This feels all kinds of insecure, is that the official way to do it?
Index: src/distrib/utils/embedded/files/ec2_init
diff -u /dev/null
On Thu, 22 Nov 2018, Aymeric Vincent wrote:
src/distrib/utils/embedded/files: armv7_boot.cmd
You shouldn't set fdtfile in this script because U-Boot already sets it.
From socfpga_de0_nano_soc_defconfig:
CONFIG_DEFAULT_FDT_FILE="socfpga_cyclone5_de0_nano_soc.dtb"
This way, if you
On Sat, 20 Oct 2018, Ryo Shimizu wrote:
I think the dts should be fixed rather than #ifdef __arm__
I agree that we need to change dts to eliminate 32bit enable method from
the dtb for 64bit. However, it is also strange that enable-method code
for 32bit ARM remains in the 64bit binary as well.
Hi Jaromir --
This change breaks the build of the one kernel that includes this code
(evbarm GENERIC64) as intr_establish_xname is not an MI API.
Cheers,
Jared
On Mon, 15 Oct 2018, Jaromir Dolecek wrote:
Module Name:src
Committed By: jdolecek
Date: Mon Oct 15 06:58:08 UTC
On Wed, 19 Sep 2018, Aymeric Vincent wrote:
Module Name:src
Committed By: aymeric
Date: Wed Sep 19 17:31:39 UTC 2018
Added Files:
src/sys/arch/arm/altera: cycv_clkmgr.c cycv_dwcmmc.c cycv_gmac.c
cycv_intr.h cycv_platform.c cycv_reg.h cycv_rstmgr.c cycv_var.h
On Sun, 19 Aug 2018, Rin Okuyama wrote:
On 2018/08/18 22:41, Jared McNeill wrote:
Not sure I understand this change. arm32 should be defined on 32-bit evbarm
platforms via std.evbarm.
If arm32 is not defined, I wouldn't expect a kernel to link as there are
dependencies on it in arch/arm
Not sure I understand this change. arm32 should be defined on 32-bit
evbarm platforms via std.evbarm.
If arm32 is not defined, I wouldn't expect a kernel to link as there are
dependencies on it in arch/arm/conf/files.arm as well.
On Sat, 18 Aug 2018, Rin Okuyama wrote:
Module Name:
> On Jun 20, 2018, at 4:25 PM, Jason Thorpe wrote:
>
>> On Jun 20, 2018, at 9:56 AM, Jared McNeill wrote:
>>
>> On Wed, 20 Jun 2018, Jason Thorpe wrote:
>>
>>> ofctl(8) is pretty useless for this purpose because it doesn't show you
>>> whic
On Wed, 20 Jun 2018, Jason Thorpe wrote:
ofctl(8) is pretty useless for this purpose because it doesn't show you which
driver instance has attached to a given device tree node. As for passing
generic boot args, it's not obvious how one does that on the RPI (and I don't
even see the hook
Not a fan of this, some of these paths can get fairly long (boot the
VEXPRESS_A15 kernel to see for yourself) and the path is
only really useful if you are debugging something.
If you want to see the debugging information we already have a way to
do that with boot -x. You can also inspect the
The -l flag dumps a partial tree starting with the node specified by
'file'. The format of the output is the same as when you run ofctl with no
arguments (this dumps the full tree, equivalent of 'ofctl -l /').
It looks like -r and -w will tell ofctl to read from or write to an
externalized
Where did you get the compat strings used in tsllux_compats? Linux uses
"amstaos" as vendor prefix, and always exact chip IDs (never anything like
tsl256x).
On Sun, 27 May 2018, Jason R Thorpe wrote:
Module Name:src
Committed By: thorpej
Date: Sun May 27 05:31:20 UTC 2018
On Sun, 8 Apr 2018, m...@netbsd.org wrote:
Can we talk to someone with legal expertise before importing code under
this license?
Thank you for your concern. This change was discussed with and approved by
board.
Hi Manuel --
On Tue, 3 Apr 2018, Manuel Bouyer wrote:
Log Message:
external interrupt functions are named "eint" in the sunxi_gpio_pins[]
arrays, while sunxi_gpio_establish() looks for "eint".
Rename eint to eint in sunxi_gpio_pins[]. Tested with an external interrupt
on PH0 on an A20.
I
On Wed, 13 Dec 2017, Matt Thomas wrote:
+* Set up a preliminary mapping in the MMU to allow us to run
+* at KERNEL_BASE with caches on.
For FDT you need to add an extra entry for the DTB as the blob passed
down from U-Boot is not guaranteed to live within the region covered by
The addition of a default case to the getopt loop means refuse will not
have a chance to process built-in options.
On Sat, 25 Nov 2017, Christos Zoulas wrote:
Module Name:src
Committed By: christos
Date: Sun Nov 26 03:06:24 UTC 2017
Modified Files:
On Wed, 8 Nov 2017, Pierre Pronchery wrote:
Sorry, I could not guess that, and I currently do not have reliable
Internet at home so I often have to work on this offline. I got this
part to build, thought this was a net positive and decided to commit it
so it can benefit others too.
You are
Could have saved yourself a lot of time if you had emailed me first, I've
been sitting on this code since I ported bwfm but didn't commit it as the
original code doesn't actually work. Do you plan on finishing it?
On Tue, 7 Nov 2017, Pierre Pronchery wrote:
Module Name:src
Committed By:
On Fri, 27 Oct 2017, Utkarsh Anand wrote:
Module Name:src
Committed By: utkarsh009
Date: Fri Oct 27 09:59:17 UTC 2017
Modified Files:
src/sys/arch/x86/x86: intr.c
src/sys/ddb: db_interface.h db_panic.c
src/sys/kern: init_main.c subr_autoconf.c
On Sat, 21 Oct 2017, Robert Elz wrote:
Log Message:
Create directory for new bwfm firmware to be installed into.
Thank you!
On Fri, 20 Oct 2017, Manuel Bouyer wrote:
Any reason to not add it to other arches (especially i386) too ?
I wasn't sure it would work everywhere because there are structures used
to talk to the firmware that are defined (by both the bwfm driver and the
firmware) w/o __packed.
Are you
On Tue, 29 Aug 2017, Manuel Bouyer wrote:
But it depends on the order in which the devices are probed/attached,
isn't it ?
The MD FDT code hooks up the powerdown handler very early, in initarm:
https://nxr.netbsd.org/xref/src/sys/arch/evbarm/fdt/fdt_machdep.c#392
On Tue, 29 Aug 2017, Manuel Bouyer wrote:
I'd like to have a way to disable this (a compile-time option would be OK
for me).
On evaluation boards (like cubieboard, or olimex lime2), you may have
a power button on the board itself but you don't have a way to add an external
power button (e.g.
On Sun, 6 Aug 2017, sc dying wrote:
Does rpi_machdep.c forget to set property "disable"
in rpi_device_register?
Looks like I missed that one, thanks for spotting it. I'll prepare a patch
for pullup.
Cheers,
Jared
Thank you, I will see if I can make some progress in this area. One of my
sunxi boards has DDR52-capable eMMC.
On Mon, 17 Jul 2017, Kimihiro Nonaka wrote:
I remember that it was not working yet.
2017-07-17 3:36 GMT+09:00 Jared McNeill <jmcne...@invisible.ca>:
Does the DDR52 code w
Does the DDR52 code work? I don't see sdhc setting SMC_CAPS_MMC_DDR52
anywhere..
On Fri, 17 Feb 2017, NONAKA Kimihiro wrote:
Module Name:src
Committed By: nonaka
Date: Fri Feb 17 10:50:43 UTC 2017
Modified Files:
src/sys/dev/sdmmc: sdhc.c sdmmc_mem.c sdmmcchip.h
This breaks kernel builds:
/home/jmcneill/netbsd/cvs-src/sys/uvm/pmap/pmap_tlb.c: In function
'pmap_tlb_update_addr':
/home/jmcneill/netbsd/cvs-src/sys/uvm/pmap/pmap_tlb.c:739:13: error: implicit
declaration of function 'pte_valid_p' [-Werror=implicit-function-declaration]
Typo in awin_reg.h?
-#define AWIN_DEBE_MODCTL_OUT_SEL_LCD 0
+#define AWIN_DEBE_MODCTL_OUT_SEL_LCD0 0
+#define AWIN_DEBE_MODCTL_OUT_SEL_LCD1 0
On Tue, 3 Nov 2015, Manuel Bouyer wrote:
Module Name:src
Committed By: bouyer
Date: Tue Nov 3 18:38:03 UTC 2015
Modified Files:
A31 and A80 use different PMUs. I checked in a fix -- the axp20x specific
code in awin_machdep.c is now protected by #if NAXP20X > 0.
On Tue, 20 Oct 2015, Jeff Rizzo wrote:
On 10/17/15 8:30 AM, Manuel Bouyer wrote:
Module Name:src
Committed By: bouyer
Date: Sat Oct 17
I should have been more clear in the commit message -- I added the
dependency on gpiobutton(4), not gpio(4).
On Fri, 16 Oct 2015, Paul Goyette wrote:
Date: Fri, 16 Oct 2015 15:47:43 +0800 (PHT)
From: Paul Goyette
Reply-To: p...@whooppee.com
To:
Unless you plan on implementing a better fix, I'm going to commit
something like this (not compile tested) to restore HDMI audio
functionality for A20 and A31.
Index: awin_debe.c
===
RCS file:
On Tue, 6 Oct 2015, Manuel Bouyer wrote:
On Tue, Oct 06, 2015 at 10:06:31AM +1100, matthew green wrote:
And is this really a problem ? turning off video is configurable in the
X server, so if you want audio without video you can turn off the
screensaver ...
it's a problem if you want the
On Mon, 5 Oct 2015, Manuel Bouyer wrote:
On Mon, Oct 05, 2015 at 02:13:51PM -0300, Jared McNeill wrote:
Can you see what happens to audio output when the display is turend off in
this way? I have a vague memory of trying something like this before..
Not easily, my display doens't deal
, Manuel Bouyer wrote:
On Mon, Oct 05, 2015 at 02:42:00PM -0300, Jared McNeill wrote:
On Mon, 5 Oct 2015, Manuel Bouyer wrote:
On Mon, Oct 05, 2015 at 02:13:51PM -0300, Jared McNeill wrote:
Can you see what happens to audio output when the display is turend off in
this way? I have a vague memory
-0300, Jared McNeill wrote:
On Mon, 5 Oct 2015, Manuel Bouyer wrote:
BTW, I'm looking at this because I need to make the LVDS interface to work
(and turn the display on/off via GPIOs, to save power). Do you have ideas
on how this should work ?
We won't have EDID source in this case; for the omap
I'm seeing this error on arm now with today's autobuild:
http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201507241030Z/evbarm-earmv7hf/
armv7# pkg_info
assertion pthread__tsd_destructors[key] != NULL failed: file
/home/source/ab/HEAD/src/lib/libpthread/pthread_tsd.c, line 179,
function
I don't think wtf handles duplicate entries very well:
apsaras$ cat test EOF
TLAthree letter acronym
TLAtrue love always
EOF
apsaras$ wtf -f test TLA
TLA: three letter acronym
true love always
On Mon, 13 Apr 2015, Blue Rats wrote:
Module Name:src
Committed By: rodent
Date:
Thank you! Do you plan on requesting a pullup for netbsd-7?
On Sun, 22 Mar 2015, Adrian Steinmann wrote:
Module Name:src
Committed By: ast
Date: Sun Mar 22 09:57:42 UTC 2015
Modified Files:
src/distrib/sets/lists/base: mi
src/distrib/sets/lists/man: mi
Thank you for catching this mistake, it should have been appending to
${mnt}/etc/rc.local. I have checked in a fix.
On Thu, 12 Feb 2015, Takahiro HAYASHI wrote:
On 2015/02/07 00:15, Jared D. McNeill wrote:
Module Name:src
Committed By: jmcneill
Date: Fri Feb 6 15:15:02 UTC
Fixed commit message:
Add Xbox One controller support. Report descriptor from
https://github.com/lloeki/xbox_one_controller;
On Sun, 8 Feb 2015, Jared D. McNeill wrote:
Module Name:src
Committed By: jmcneill
Date: Sun Feb 8 19:22:45 UTC 2015
Modified Files:
On Mon, 17 Nov 2014, matthew green wrote:
hmm, does this change the module ABI? ie, kernel version bump time?
I don't think anything in sys/modules uses edidvar.h
Are you able to build the arch/evbarm/conf/CUBIEBOARD kernel with these
changes?
The kernel config has options CPU_CORTEXA7, which depends on
CPU_CORTEX, which depends on CPU_ARMV7. Neither CPU_CORTEX nor CPU_ARMV7
are defined in opt_cputypes.h
On Fri, 10 Oct 2014, Masao Uebayashi wrote:
On Fri, 5 Apr 2013, Hisashi T Fujinaka wrote:
On Sat, 6 Apr 2013, Izumi Tsutsui wrote:
If the problem is overflow of the image, shouldn't the extra variable
in each config file be bumped instead of changing a unit?
Sorry for the messy commit. I just changed the -b line the way I did
because
On Sun, 17 Feb 2013, Martin Husemann wrote:
For those happy to never been exposed to this acronym: he is talking about
the Windows User Annoyance Coolaid which campaigns with it's brother VUS
(Keep virtualy all Users Stupid) to make expert users (defined as those
users that grok the concept of a
I've updated the commit message for src/games/phantasia/Makefile r1.36 and
src/games/adventure/Makefile r1.14 to clarify the issue:
Workaround a toolchain issue by renaming the 'setup' host tool to 'mkdata'
to make UAC happy when building with Cygwin. As described here --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It doesn't have to be ELF, I do it now on x86 for splash images. From
/boot I load a .png, .jpg, or .bmp and add it to the module list but mark
it as BI_MODULE_IMAGE (instead of BI_MODULE_ELF). I can then grab the blob
from the kernel -- see
Please restore EDITOR=vi, otherwise the following message is going to
haunt me for the rest of time:
$ svn commit
svn: Commit failed (details follow):
svn: Could not use external editor to fetch log message; consider setting the
$SVN_EDITOR environment variable or using the --message (-m) or
This can't please everybody, so please nobody reasoning is why NetBSD
also ships with twm as default.
EDITOR=vi has been in /etc/skel for 11yrs now, lots of discussion about
it here: http://gnats.netbsd.org/10985
On Wed, 19 Oct 2011, Greg Troxel wrote:
Jared McNeill jmcne...@invisible.ca
I would argue that any manually loaded module shouldn't be autounloaded.
What do you think about flagging modules as autoloaded and only
autounloading the autoloaded ones?
On Tue, 18 Oct 2011, Jukka Ruohonen wrote:
On Tue, Oct 18, 2011 at 08:43:46AM +0200, Marc Balmer wrote:
Am 18.10.11
The problem is that i2c.c can be built either because some other driver
needs i2cbus or because an instance of the iic driver is requested. Only
in the latter case does CFDRIVER_DECL get added to ioconf.c. I think I'll
have to split out the driver specific stuff into a separate file to fix this
You forgot to make the iic driver detachable, modunload iic will panic I
think.
-Original Message-
From: Marc Balmer
Sent: Sunday, October 02, 2011 7:38 AM Newsgroups:
gmane.os.netbsd.devel.cvs.full
To: source-changes-full-qavaossjccednm+yrof...@public.gmane.org
Subject: CVS commit:
I have ~70 analog channels coming in along with my digital cable service.
Canada's digital OTA transition deadline is tomorrow but there are still a
few markets where analog broadcasting will continue, my hometown being one
of those places. Somewhere in storage I have a VCR with an RF output. I
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
We should not really trust ACPI/FADT here. See acpicpu(4) how this is
Why?
derived from the actual CPU information. Additionally, I suggested decreasing
the quality of tsc(9) based on this information a long time ago, but joerg@
had concerns about
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
Why?
Because we (the operating system) know this better than the BIOS writer.
And because this flag is not reliable; numerous systems where tsc(9) is
broken miss this flag in my ACPI table collection, and vice versa.
This flag is new in ACPI v3.0. If
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
Yes, but when possible, we should always prefer actual, reliable, CPU
information instead of the BIOS. Note also that at least with Intel CPUs,
the TSC should be entirely safe with the current stock-NetBSD (i.e. no
automatic CPU power management), but
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
On Mon, Aug 08, 2011 at 08:16:43AM -0400, Jared McNeill wrote:
Newer systems with invariant TSC shouldn't set the USE_PLATFORM_CLOCK
flag.
But the do, unfortunately. Again, I have several examples from the field.
I'd be willing to let CPUID
On Tue, 8 Mar 2011, Michael Lorenz wrote:
Modified Files:
src/sys/arch/x86/x86: x86_autoconf.c
lol
On Mon, 21 Feb 2011, matthew green wrote:
well, i dunno about others but i've found that the old modules
lying around tends to fill up space pretty quickly, but ignoring
that problem and looking at recent i386 builds, i see that the
MONOLITHIC kernel set is only 440kb larger than GENERIC, yet
88 matches
Mail list logo