Link [ NetBSD | NetBSD OpenGrok source search | PR fulltext-search | Summary of daily snapshot builds | history of daily build result | pkgsrc commit viewer ]


   
        usage: [branch:branch] [user:user] [path@revision] keyword [... [-excludekeyword [...]]] (e.g. branch:MAIN sys/arch/arm, if_wm.c@1.234 )




switch to index mode

recent branches: MAIN (0m)  netbsd-8 (5d)  netbsd-10 (5d)  netbsd-9 (11d)  thorpej-ifq (175d)  thorpej-altq-separation (178d) 

2024-05-10 08:10:25 UTC Now

2017-06-08 04:00:01 UTC MAIN commitmail json YAML

add some pool_allocators for pool item sizes larger than PAGE_SIZE.
needed by dtrace.

(chs)

2017-06-08 03:42:37 UTC MAIN commitmail json YAML

As (briefly) discussed on current-users, change the way that MAKEDEV checks
for more than one of the  -m -p -s -t args (and checks whether any were given
to pick one if not) to be more shell friendly.

Note that while the method here is the same as was discussed on the list,
the actual implementation is free of the typos, and just pure lunacy that
was in the code that was shown there.

Also note these changes are intended to be completely internal, there
should be no visible impact upon the way that MAKEDEV works.

ok:christos.  Thanks to pgoyette for the code review.

(kre)

2017-06-08 03:39:18 UTC MAIN commitmail json YAML

For the Target Link Speed in LCSR2, 0 is allowed for a device which supports
2.5GT/s only (and this check also works for devices which compliant to
versions of the base specification prior to 3.0.

Tested with BCM5709:
-      Target Link Speed: unknown value (0)
+      Target Link Speed: 2.5GT/s

(msaitoh)

2017-06-08 03:25:03 UTC MAIN commitmail json YAML

this file uses the <sys/queue.h> macros so it should include
that header itself, rather than relying on getting it indirectly
by including some other header (which will soon be changed
to not do that anymore).

(chs)

2017-06-08 03:02:26 UTC MAIN commitmail json YAML

sanitize count used for kmem_alloc size.

Hmm, who uses CIOCNGSESSION, CIOCNFSESSION, CIOCNCRYPTM or CIOCNFKEYM?

(knakahara)

2017-06-08 02:27:30 UTC MAIN commitmail json YAML

- Add some missing baudrate entries
- Add 1000BASE-KX and 2500BASE-KX

(msaitoh)

2017-06-08 02:25:43 UTC MAIN commitmail json YAML

I am an idiot...  revert the previous unintended commit.

(kre)

2017-06-08 02:23:52 UTC MAIN commitmail json YAML

Improve the (new) LINENO section, markup changes (with thanks to wiz@ for
assistace) and some better wording in a few placed.

(kre)

2017-06-08 01:23:01 UTC MAIN commitmail json YAML

move some buffer cache internals declarations from buf.h to vfs_bio.c.
this is needed to avoid name conflicts with ZFS and also
makes it clearer that other code shouldn't be messing with these.
remove the LFS debug code that poked around in bufqueues and
remove the BQ_EMPTY bufqueue since nothing uses it anymore.
provide a function to let LFS and wapbl read the value of nbuf for now.

(chs)

2017-06-08 01:09:52 UTC MAIN commitmail json YAML

allow cv_signal() immediately followed by cv_destroy().
this sequence is used by ZFS in a couple places and by supporting it
natively we can undo our local ZFS changes that avoided it.
note that this is only legal when all of the waiters use cv_wait()
and not any of the other variations, and lockdebug will catch
any violations of this rule.

(chs)

2017-06-08 00:17:02 UTC MAIN commitmail json YAML

Put back crypto_checkdriver(); use it when we need to make sure that we
get back a cryptocap that has been initialized.

(christos)

2017-06-07 22:59:42 UTC MAIN commitmail json YAML

Change t_sprintf to an expected failure, since we don't respect the empty
thousands separator of the C/POSIX locale (PR standards/52282).

(perseant)

2017-06-07 20:54:59 UTC MAIN commitmail json YAML

EV_SET(2) - simplify description

Note only the information that it does not evaluate multiple times its
parameters.

Suggested by <wiz>.

(kamil)

2017-06-07 15:24:50 UTC MAIN commitmail json YAML

2017-06-07 13:50:57 UTC MAIN commitmail json YAML

Add missing argument to macro.

(wiz)

2017-06-07 13:49:48 UTC MAIN commitmail json YAML

New sentence, new line. Whitespace.

(wiz)

2017-06-07 10:38:34 UTC MAIN commitmail json YAML

Hook in dtc/libfdt now that it builds for me

(skrll)

2017-06-07 09:31:30 UTC MAIN commitmail json YAML

PR bin/52280

removescapes_nl in expari() even when not quoted,
CRTNONL's appear regardless of quoting (unlike CTLESC).

(kre)

2017-06-07 09:14:32 UTC MAIN commitmail json YAML

Change the deprecation notice about ofwboot.elf to say that it may
still be required in some cases, as observed by some MacMini users.

(he)

2017-06-07 08:45:51 UTC MAIN commitmail json YAML

fix tlb_record_asids 2nd arg to match usage - it's a maximum asid value
and not a mask

(skrll)

2017-06-07 08:10:31 UTC MAIN commitmail json YAML

Undo some over agressive fixes for a (pre-commit) bug that did not
need these changes to be fixed - and these cause problems in another
absurd use case.  Either of these issues is unlikely to be seen by
anyone who isn't an idiot masochist...

(kre)

2017-06-07 08:07:51 UTC MAIN commitmail json YAML

Set the line number before expanding args, not after.  As the line_number
would have usually been set earlier, this change is mostly an effective
no-op, but it is better this way (just in case) - not observed to have
caused any problems.

(kre)

2017-06-07 08:06:22 UTC MAIN commitmail json YAML

Unbreak (at least) i386 build .... I have no idea why this built for me on
amd64 (problem was missing prototype for snprintf witout <stdio.h>)

While here, add some (DEBUG mode only) tracing that proved useful in
solving another problem.

(kre)

2017-06-07 07:06:26 UTC MAIN commitmail json YAML

Use __BIT().  No functional change.

(skrll)

2017-06-07 05:30:49 UTC MAIN commitmail json YAML

Fix to print the following bit fields correctly.
  -  Supported Link Speeds Vector in LCAP2
  -  Lower SKP OS Generation Supported Speed Vector  in LCAP2
  -  Lower SKP OS Reception Supported Speed Vector in LCAP2
  -  Enable Lower SKP OS Generation Vector in LCTL3

Note that the above bitfields start from 0 and the follwing bitfields start
from 1:
  -  Maximum Link Speed in LCAP
  -  Current Link Speed in LCSR
  -  Target Link Speed in LCSR2

(msaitoh)

2017-06-07 05:26:19 UTC MAIN commitmail json YAML

s/filesystem/file system/

Thanks to Thomas for pointing out that in NetBSD man pages we try to use the convention of writing it
as "file system".

(abhinav)

2017-06-07 05:08:32 UTC MAIN commitmail json YAML

A better LINENO implementation.  This version deletes (well, #if 0's out)
the LINENO hack, and uses the LINENO var for both ${LINENO} and $((LINENO)).
(Code to invert the LINENO hack when required, like when de-compiling the
execution tree to provide the "jobs" command strings, is still included,
that can be deleted when the LINENO hack is completely removed - look for
refs to VSLINENO throughout the code.  The var funclinno in parser.c can
also be removed, it is used only for the LINENO hack.)

This version produces accurate results: $((LINENO)) was made as accurate
as the LINENO hack made ${LINENO} which is very good.  That's why the
LINENO hack is not yet completely removed, so it can be easily re-enabled.
If you can tell the difference when it is in use, or not in use, then
something has broken (or I managed to miss a case somewhere.)

The way that LINENO works is documented in its own (new) section in the
man page, so nothing more about that, or the new options, etc, here.

This version introduces the possibility of having a "reference" function
associated with a variable, which gets called whenever the value of the
variable is required (that's what implements LINENO).  There is just
one function pointer however, so any particular variable gets at most
one of the set function (as used for PATH, etc) or the reference function.
The VFUNCREF bit in the var flags indicates which func the variable in
question uses (if any - the func ptr, as before, can be NULL).

I would not call the results of this perfect yet, but it is close.

(kre)

2017-06-07 04:44:17 UTC MAIN commitmail json YAML

An initial attempt at implementing LINENO to meet the specs.

Aside from one problem (not too hard to fix if it was ever needed) this version
does about as well as most other shell implementations when expanding
$((LINENO)) and better for ${LINENO} as it retains the "LINENO hack" for the
latter, and that is very accurate.

Unfortunately that means that ${LINENO} and $((LINENO)) do not always produce
the same value when used on the same line (a defect that other shells do not
share - aside from the FreeBSD sh as it is today, where only the LINENO hack
exists and so (like for us before this commit) $((LINENO)) is always either
0, or at least whatever value was last set, perhaps by
LINENO=${LINENO}
which does actually work ... for that one line...)

This could be corrected by simply removing the LINENO hack (look for the string
LINENO in parser.c) in which case ${LINENO} and $((LINENO)) would give the
same (not perfectly accurate) values, as do most other shells.

POSIX requires that LINENO be set before each command, and this implementation
does that fairly literally - except that we only bother before the commands
which actually expand words (for, case and simple commands).  Unfortunately
this forgot that expansions also occur in redirects, and the other compound
commands can also have redirects, so if a redirect on one of the other compound
commands wants to use the value of $((LINENO)) as a part of a generated file
name, then it will get an incorrect value.  This is the "one problem" above.
(Because the LINENO hack is still enabled, using ${LINENO} works.)

This could be fixed, but as this version of the LINENO implementation is just
for reference purposes (it will be superseded within minutes by a better one)
I won't bother.  However should anyone else decide that this is a better choice
(it is probably a smaller implementation, in terms of code & data space then
the replacement, but also I would expect, slower, and definitely less accurate)
this defect is something to bear in mind, and fix.

This version retains the *BSD historical practice that line numbers in functions
(all functions) count from 1 from the start of the function, and elsewhere,
start from 1 from where the shell started reading the input file/stream in
question.  In an "eval" expression the line number starts at the line of the
"eval" (and then increases if the input is a multi-line string).

Note: this version is not documented (beyond as much as LINENO was before)
hence this slightly longer than usual commit message.

(kre)

2017-06-07 03:53:11 UTC MAIN commitmail json YAML

vlan(4) MP-ify. contributed by s-yamaguchi@IIJ, thanks.

XXX Pull-ups needed for netbsd-8 branch

(knakahara)

2017-06-07 03:32:39 UTC MAIN commitmail json YAML

2017-06-07 03:21:31 UTC MAIN commitmail json YAML

- Add some bit definitions:
  - Unidirectional enable
  - Unidirectional ability
  - Extended Next Page
  - Receive Next Page Location Able
  - Received Next Page Storage Location
  - Data Link Layer Classification capability
  - Enable Physical Layer Classification
  - Invalid Class in PD Class
  - PSE Status bit definitions
- Sort registers
- Modify comments.

(msaitoh)

2017-06-07 03:08:44 UTC MAIN commitmail json YAML

2017-06-06 22:38:52 UTC MAIN commitmail json YAML

Fix a typo (or rather a remnant of an earlier intent).

(kre)

2017-06-06 21:01:07 UTC MAIN commitmail json YAML

Fix a race between ld_sdmmc_start and ld_sdmmc_dobio that could result in
tasks getting lost from the task queue. The symptom of this is a NULL
deref in ld_sdmmc_start since the code assumes that a task will always be
available from the pool.

This changes the code to use pcq(9) instead of a TAILQ to manage the free
task list.

(jmcneill)

2017-06-06 20:19:04 UTC MAIN commitmail json YAML

2017-06-06 20:12:54 UTC MAIN commitmail json YAML

Bump date for previous
Fix typo: fileystem -> filesystem

(abhinav)

2017-06-06 19:59:10 UTC MAIN commitmail json YAML

whitespace police

(ryo)

2017-06-06 19:48:42 UTC MAIN commitmail json YAML

since ln(1) now uses linkat(2) provide a dumb wrapper.

(christos)

2017-06-06 18:08:23 UTC MAIN commitmail json YAML

- acquire lock
- use c99 loop indexes
- initialize featp

(christos)

2017-06-06 17:01:59 UTC MAIN commitmail json YAML

Update the EV_SET() description with newer implementation.

EV_SET(2) is a macro again, that wraps an inline function which is still
new in NetBSD 8.0.

Sponsored by <The NetBSD Foundation>

(kamil)

2017-06-06 16:29:36 UTC netbsd-8 commitmail json YAML

2017-06-06 16:26:53 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by jmcneill in ticket #13):
sys/arch/arm/fdt/plfb_fdt.c: revision 1.2
sys/arch/arm/vexpress/vexpress_platform.c: revision 1.3
sys/arch/evbarm/conf/VEXPRESS_A15: revision 1.13
sys/arch/evbarm/fdt/fdt_machdep.c: revisions 1.5, 1.6
sys/dev/ic/pl050.c: revision 1.2
Fix spelling of WS_DEFAULT_FG and WS_KERNEL_FG options.
--
Attach kbd slot to console
--
Allow plfb to be the console device
--
Add support for stdout-path= kernel cmdline option to override the
console device specified in the FDT.
--
Initialize boot_args before bootstrap for the benefit of platform code.
--
Allow 'console=fb' to act as a shortcut on vexpress for
'stdout-path=/smb@08000000/motherboard/iofpga@3,00000000/clcd@1f0000'

(snj)

2017-06-06 15:58:59 UTC MAIN commitmail json YAML

2017-06-06 15:58:17 UTC MAIN commitmail json YAML

2017-06-06 12:56:43 UTC MAIN commitmail json YAML

Document current dtc/libfdt status (even if it is a mess)

(skrll)

2017-06-06 09:56:57 UTC MAIN commitmail json YAML

Allow 'console=fb' to act as a shortcut on vexpress for
'stdout-path=/smb@08000000/motherboard/iofpga@3,00000000/clcd@1f0000'

(jmcneill)

2017-06-06 09:56:00 UTC MAIN commitmail json YAML

Initialize boot_args before bootstrap for the benefit of platform code.

(jmcneill)

2017-06-06 09:31:21 UTC netbsd-8 commitmail json YAML

2017-06-06 09:30:24 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by sevan in ticket #12):
external/bsd/blacklist/bin/blacklistd.conf.5: revision 1.6
Improve wording.
Bump date.
ok christos

(martin)

2017-06-06 09:28:26 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by skrll in ticket #11):
sys/gdbscripts/cpus: revision 1.2
sys/gdbscripts/cpus: revision 1.3
Make cpus MI
Typo in previous

(martin)

2017-06-06 09:25:49 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by skrll in ticket #10):
sys/arch/mips/mips/pmap_machdep.c: revision 1.20
Fix the PMAP_NO_PV_UNCACHED pmap_md_vca_add case where the pmap_update
call would cause problems for pmap_remove_all case where the deferred
activate should not be done...
Add a comment about what's going on.

(martin)

2017-06-06 09:20:14 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by sborrill in ticket #9):
usr.sbin/service/service: revision 1.8
Only match first instance of name and rcvar in file.

(martin)

2017-06-06 08:21:53 UTC MAIN commitmail json YAML

Disable dtc/libfdt for now

(skrll)

2017-06-06 07:45:39 UTC MAIN commitmail json YAML

2017-06-06 07:32:41 UTC MAIN commitmail json YAML

Style change.

(nat)

2017-06-06 07:31:41 UTC MAIN commitmail json YAML

pad blocksize 1024 -> 8192.  Helps when sleeping in rate limiter.

(nat)

2017-06-06 07:29:35 UTC MAIN commitmail json YAML

Simplification of rate limiter.  It now works uni/multiprocessor.

(nat)

2017-06-06 07:28:29 UTC netbsd-8 commitmail json YAML

2017-06-06 07:27:15 UTC MAIN commitmail json YAML

sc_bytes_count needs to be set in pad_audio_open not pad_open.

(nat)

2017-06-06 07:18:38 UTC MAIN commitmail json YAML

Express BYTESTOSLEEP as an 64 bit integer.
Use BYTESTOSLEEP in expresson of BYTES_PER_SEC.

(nat)

2017-06-06 07:13:06 UTC MAIN commitmail json YAML

Fix a typo, i366 -> i386.
From PR misc/52274.

(mbalmer)

2017-06-06 05:39:28 UTC MAIN commitmail json YAML

2017-06-06 05:39:06 UTC MAIN commitmail json YAML

- Change VMware's 0x0770 from "Virtual USB" to "Virtual EHCI"
- Add VMware's 0x0774(UHCI) and 0x0778(xHCI)

(msaitoh)

2017-06-06 04:56:12 UTC MAIN commitmail json YAML

Add missing RCS Id.

(msaitoh)

2017-06-06 04:11:41 UTC MAIN commitmail json YAML

apply the same fix as crypto.c:r1.83 for crypto_dispatch to crypto_kdispatch.

(knakahara)

2017-06-06 01:51:39 UTC MAIN commitmail json YAML

avoid crp_q reordering as hardware interrupts.

crypto_{,k}invoke() can be called with holding crp_q_mtx now.

(knakahara)

2017-06-06 01:48:34 UTC MAIN commitmail json YAML

2017-06-06 01:47:23 UTC MAIN commitmail json YAML

restructure locks(2/2): crypto_q_mtx can be adaptive now.

(knakahara)

2017-06-06 01:45:57 UTC MAIN commitmail json YAML

restructure locks(1/2): make relation between lock and data explicit.

    + crypto_drv_mtx protects
      -  whole crypto_drivers
    + crypto_drivers[i].cc_lock (new) protects
      - crypto_drivers[i] itself
      - member of crypto_drivers[i]
    + crypto_q_mtx protects
      - crp_q
      - crp_kq
    + crypto_ret_q_mtx protects
      - crp_ret_q
      - crp_ret_kq
      - crypto_exit_flag

I will add locking note later.

(knakahara)

2017-06-06 00:28:05 UTC MAIN commitmail json YAML

Add support for stdout-path= kernel cmdline option to override the
console device specified in the FDT.

(jmcneill)

2017-06-06 00:26:59 UTC MAIN commitmail json YAML

Allow plfb to be the console device

(jmcneill)

2017-06-06 00:26:17 UTC MAIN commitmail json YAML

Attach kbd slot to console

(jmcneill)

2017-06-06 00:25:48 UTC MAIN commitmail json YAML

Fix spelling of WS_DEFAULT_FG and WS_KERNEL_FG options.

(jmcneill)

2017-06-05 23:55:43 UTC MAIN commitmail json YAML

No need to set dtc twice.

(christos)

2017-06-05 23:45:23 UTC MAIN commitmail json YAML

2017-06-05 23:44:27 UTC MAIN commitmail json YAML

2017-06-05 23:44:08 UTC MAIN commitmail json YAML

2017-06-05 23:41:52 UTC MAIN commitmail json YAML

2017-06-05 23:24:29 UTC MAIN commitmail json YAML

2017-06-05 22:44:40 UTC MAIN commitmail json YAML

tools build glue.

(christos)

2017-06-05 21:34:58 UTC MAIN commitmail json YAML

Improve wording.
Bump date.

ok christos

(sevan)

2017-06-05 21:19:33 UTC MAIN commitmail json YAML

Undo the previous

While it fixed the problem of trailing spaces, but if the probe specifier
contained leading spaces, it would brake dtrace. The proper fix would be
to skip the leading spaces in the string as well.

However, it would result in a bigger diff for a very small benefit. While
a new import of dtrace is impending, it's better not to have this change.

Discussed with christos.

(abhinav)

2017-06-05 20:02:11 UTC MAIN commitmail json YAML

Clean out some #if 0'ed or //'ed code

(skrll)

2017-06-05 19:17:59 UTC MAIN commitmail json YAML

remove the conflict.

(christos)

2017-06-05 18:59:43 UTC MAIN commitmail json YAML

2017-06-05 18:59:21 UTC MAIN commitmail json YAML

Make this compatible with byacc

(christos)

2017-06-05 18:59:10 UTC MAIN commitmail json YAML

rename include file per our convention.

(christos)

2017-06-05 18:56:16 UTC MAIN commitmail json YAML

2017-06-05 18:54:31 UTC MAIN commitmail json YAML

2017-06-05 18:44:13 UTC MAIN commitmail json YAML

Typo in previous

(skrll)

2017-06-05 18:34:16 UTC MAIN commitmail json YAML

2017-06-05 17:11:10 UTC MAIN commitmail json YAML

Fix the trailing space in the probe specifier's name in dtrace(1)'s output.

When using dtrace using one of the tracing options, such as -n, -P, -i, -f etc.,
the first line of output from dtrace one is something like this:

sudo dtrace -n 'syscall:::entry /pid == 100/ {@num[probefunc] = count();}'
dtrace: description 'syscall:::entry ' matched 482 probes

There is a trailing space at the end of the probe specifier name ('syscall:::entry ').
This happens beucase dtrace tries to separate the probe name from the predicate and actions
using `{' and `/' as the separators but doesn't consider space also as a possible separator.

Output after this change:
sudo dtrace -n 'syscall:::entry /pid == 100/ {@num[probefunc] = count();}'
dtrace: description 'syscall:::entry' matched 482 probes

ok christos@

(abhinav)

2017-06-05 15:20:51 UTC MAIN commitmail json YAML

a config for PCIe PowerMac G5 models
should have been committed years ago...

(macallan)

2017-06-05 13:35:33 UTC MAIN commitmail json YAML

Add missing return to print the Slot Power Limit Value correctly.

(msaitoh)

2017-06-05 13:15:13 UTC MAIN commitmail json YAML

Removed unused file

(skrll)

2017-06-05 10:45:36 UTC MAIN commitmail json YAML

Fix the PMAP_NO_PV_UNCACHED pmap_md_vca_add case where the pmap_update
call would cause problems for pmap_remove_all case where the deferred
activate should not be done...

Add a comment about what's going on.

(skrll)

2017-06-05 09:20:05 UTC MAIN commitmail json YAML

Only match first instance of name and rcvar in file.

(sborrill)

2017-06-05 09:09:13 UTC MAIN commitmail json YAML

fix reading crp_q without holding crypto_q_mtx

(knakahara)

2017-06-05 09:07:46 UTC MAIN commitmail json YAML

use crypto_checkdriver_uninit() when it may touch uninitialized crypto_drivers.

(knakahara)

2017-06-05 08:50:07 UTC MAIN commitmail json YAML

No functional change:
- Relocate definitions in the following order to be easy to understand.
0) IFM_*MASK
1) macros to extract various bits of information from the media word.
2) Media type.
3) Shared media sub-type.
4) Status bits.
5) Shared (global) options
6) Media dependent definitions.
7) kernel function declarations.
7) userland function declarations.
- Add comments.

This change makes me realize that:
0) RFU bit have never used.
1) bit 1..0 are shared between Shared media sub-type and Status bits.
    It's little dangerous.
2) No. 5 of Media type is not used (hole).
3) Only IEEE80211 uses IFM_MMASK(IFM_MODE()) bits.
4) IFM_TOKEN's OMASK bits doesn't start from 0x00000100 but starts from
    0x00000200. Is this for BSD/OS compatibility?

(msaitoh)

2017-06-05 08:21:39 UTC netbsd-8 commitmail json YAML

2017-06-05 08:20:36 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by skrll in ticket #8):
sys/arch/arm/cortex/gic.c: revision 1.22
Initialise all the SGI/PPI priorities for all CPUs to mask the interrupts

(snj)

2017-06-05 08:15:16 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by kre in ticket #7):
bin/sh/expand.c: revisions 1.111, 1.112
PR bin/52272 - fix an off-by one that broke ~ expansions.
--
Another arithmetic expansion recordregion() fix, this time
calculate the lenght (used to calculate the end) based upon the
correct starting point.
Thanks to John Klos for finding and reporting this one.

(snj)

2017-06-05 08:13:05 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by pgoyette in ticket #6):
sys/dev/hdaudio/hdaudio.c: revision 1.5
sys/dev/pci/hdaudio_pci.c: revision 1.8
Move the hdaudio_cd out of the hdaudio_pci module and into the main
hdaudio module.  Rearrange the inter-module dependencies accordingly.
Should resolve (my) PR kern/49836

(snj)

2017-06-05 08:10:24 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by kre in ticket #5):
bin/sh/cd.c: revision 1.48
bin/sh/eval.c: revision 1.141
bin/sh/exec.c: revision 1.48
bin/sh/exec.h: revision 1.25
bin/sh/mail.c: revisions 1.17, 1.18
bin/sh/sh.1: revision 1.147
Make cd (really) do cd -P, and not just claim that is what it is doing
while doing a half-hearted, broken, partial, version of cd -L instead.
The latter (as the manual says) is not supported, what's more, it is an
abomination, and should never be supported (anywhere.)
Fix the doc so that the pretense that we notice when a path given crosses
a symlink (and turns on printing of the destination directory) is claimed
no more (that used to be true until late Dec 2016, but was changed).  Now
the print happens if -o cdprint is set, or if an entry from CDPATH that is
not "" or "." is used (or if the "cd dest repl" cd cmd variant is used.)
Fix CDPATH processing: avoid the magic '%' processing that is used for
PATH and MAILPATH from corrupting CDPATH.  The % magic (both variants)
remains undocumented.
Also, don't double the '/' if an entry in PATH or CDPATH ends in '/'
(as in CDPATH=":/usr/src/").  A "cd usr.bin" used to do
chdir("/usr/src//usr.bin").  No more.  This is almost invisible,
and relatively harmless, either way....
Also fix a bug where if a plausible destination directory in CDPATH
was located, but the chdir() failed (eg: permission denied) and then
a later "." or "" CDPATH entry succeeded, "print" mode was turned on.
That is:
cd /tmp; mkdir bin
mkdir -p P/bin; chmod 0 P/bin
CDPATH=/tmp/P:
cd bin
would cd to /tmp/bin (correctly) but print it (incorrectly).
Also when in "cd dest replace" mode, if the result of the replacement
generates '-' as the path named, as in:
cd $PWD -
then simply change to '-' (or attempt to, with CDPATH search), rather
than having this being equivalent to "cd -")
Because of these changes, the pwd command (and $PWD) essentially
always acts as pwd -P, even when called as pwd -L (which is still
the default.)  That is, even more than it did before.
Also fixed a (kind of minor) mem management error (CDPATH related)
"whosoever shall padvance must stunalloc before repeating" (and the
same for MAILPATH).
--
If we are going to keep the MAILPATH % hack, then at least do something
rational.  Since it isn't documented, what "rational" is is up for
discussion, but what it did before was not it (it was nonsense...).

(snj)

2017-06-05 07:47:32 UTC MAIN commitmail json YAML

Add an XXX about the missing flags so it's not buried in a commit
message.

now the XXX count for LFS is 260

(maya)

2017-06-05 07:35:23 UTC MAIN commitmail json YAML

Fix buggy dhcrelay(8) requirement to stay in foreground

This version of dhcrelay(8) needed to stay inforeground with -d flag in
order to service requests. Running inbackground turned it deaf to DHCP
requests.

This was caused by wrong kqueue(2) usage, where kevent(2) was used with
a file descriptor obtained by a kqueue(2) call done before fork(2).
kqueue(2) man page says "The queue is not inherited by a child created
with fork(2)". As a result, kevent(2) calls always got EBADF.

The fix is to reorder function calls in dhcrelay(8) main() function.
dhcp_context_create(), which causes kqueue(2) to be invoked, is
moved with its dependencies after fork(2). This matches the code layout
of dhclient(8) and dhcpd(8), which do not have the bug.

The fix was not submitted upstream since latest ISC DHCP code was
refactored and does not have the bug anymore.

(manu)

2017-06-05 02:15:55 UTC MAIN commitmail json YAML

Another arithmetic expansion recordregion() fix, this time
calculate the lenght (used to calculate the end) based upon the
correct starting point.

Thanks to John Klos for finding and reporting this one.

(kre)

2017-06-05 01:29:21 UTC MAIN commitmail json YAML

Correct confusion between i_flag and i_flags
These will have to be renamed.

Spotted by Riastradh, thanks!

(maya)

2017-06-05 01:01:42 UTC MAIN commitmail json YAML

Move definition of IN_ALLMOD near the flag it's a mask for.

Now we can see that it doesn't match all the flags, but changing that will
require more careful thought.

(maya)

2017-06-04 23:40:31 UTC MAIN commitmail json YAML

PR bin/52272 - fix an off-by one that broke ~ expansions.

(kre)

2017-06-04 23:34:55 UTC MAIN commitmail json YAML

Move the hdaudio_cd out of the hdaudio_pci module and into the main
hdaudio module.  Rearrange the inter-module dependencies accordingly.

Should resolve (my) PR kern/49836

XXX Pull-ups needed for netbsd-8 branch

(pgoyette)

2017-06-04 21:03:21 UTC MAIN commitmail json YAML

allow build to proceed despite system header warnings.

(christos)

2017-06-04 20:47:25 UTC netbsd-8 commitmail json YAML

2017-06-04 20:46:54 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by jmcneill in ticket #4):
sys/arch/evbarm/vexpress/vexpress_start.S: revision 1.5
Add a 1MB mapping to the MMU init table to cover the FDT blob in case the
bootloader places it beyond the init mem size.

(bouyer)

2017-06-04 20:45:54 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by jmcneill in ticket #3):
sys/dev/sdmmc/sdmmcvar.h: revision 1.24
sys/dev/sdmmc/sdmmc_mem.c: revision 1.57
sys/dev/ic/pl181.c: revision 1.4
Give a hint to controllers in the command flags if we are performing a
transfer with an SDHC capable card. If the controller needs to adjust
command args, it can use this hint to understand how it is encoded.
Re-introduce support for multi-block transfers and split transfers to fit
within the 65535-byte limit.

(bouyer)

2017-06-04 20:35:45 UTC netbsd-8 commitmail json YAML

2017-06-04 20:35:02 UTC netbsd-8 commitmail json YAML

pullup the following revisions, requested by hannken in ticket #2:
src/share/man/man9/fstrans.9 1.25
src/sys/kern/vfs_mount.c 1.66
src/sys/kern/vfs_subr.c 1.468
src/sys/kern/vfs_trans.c 1.46
src/sys/kern/vfs_vnode.c 1.94, 1.95, 1.96
src/sys/kern/vnode_if.c 1.105, 1.106
src/sys/kern/vnode_if.sh 1.65, 1.66
src/sys/kern/vnode_if.src 1.76
src/sys/miscfs/genfs/genfs_io.c 1.69
src/sys/miscfs/genfs/genfs_vnops.c 1.196, 1.197
src/sys/miscfs/genfs/layer_extern.h 1.40
src/sys/miscfs/genfs/layer_vfsops.c 1.51
src/sys/miscfs/genfs/layer_vnops.c 1.67
src/sys/miscfs/nullfs/null_vnops.c 1.42
src/sys/miscfs/overlay/overlay_vnops.c 1.24
src/sys/miscfs/umapfs/umap_vnops.c 1.60
src/sys/rump/include/rump/rumpvnode_if.h 1.29, 1.30
src/sys/rump/librump/rumpkern/emul.c 1.182
src/sys/rump/librump/rumpvfs/rumpvnode_if.c 1.29, 1.30
src/sys/sys/fstrans.h 1.11
src/sys/sys/vnode.h 1.278
src/sys/sys/vnode_if.h 1.100, 1.101
src/sys/sys/vnode_impl.h 1.14, 1.15
src/sys/ufs/lfs/lfs_pages.c 1.12

Vnode state, lock and fstrans cleanup:
- Rename vnode state "VS_ACTIVE" to "VS_LOADED" and add synthetic
  state "VS_ACTIVE" to assert a loaded vnode with usecount > 0.

- Redo FSTRANS in vnode_if.c and use it for VOP_LOCK and VOP_UNLOCK.

- Cleanup the genfs lock operations.

- Make "struct vnode_impl" member "vi_lock" a krwlock_t again.

- Remove the lock type argument from fstrans_start and
  fstrans_start_nowait,
  remove now unused FSTRANS state "FSTRANS_SUSPENDING".

(bouyer)

2017-06-04 20:28:13 UTC MAIN commitmail json YAML

If we are going to keep the MAILPATH % hack, then at least do something
rational.  Since it isn't documented, what "rational" is is up for
discussion, but what it did before was not it (it was nonsense...).

(kre)

2017-06-04 20:27:14 UTC MAIN commitmail json YAML

Make cd (really) do cd -P, and not just claim that is what it is doing
while doing a half-hearted, broken, partial, version of cd -L instead.
The latter (as the manual says) is not supported, what's more, it is an
abomination, and should never be supported (anywhere.)

Fix the doc so that the pretense that we notice when a path given crosses
a symlink (and turns on printing of the destination directory) is claimed
no more (that used to be true until late Dec 2016, but was changed).  Now
the print happens if -o cdprint is set, or if an entry from CDPATH that is
not "" or "." is used (or if the "cd dest repl" cd cmd variant is used.)

Fix CDPATH processing: avoid the magic '%' processing that is used for
PATH and MAILPATH from corrupting CDPATH.  The % magic (both variants)
remains undocumented.

Also, don't double the '/' if an entry in PATH or CDPATH ends in '/'
(as in CDPATH=":/usr/src/").  A "cd usr.bin" used to do
chdir("/usr/src//usr.bin").  No more.  This is almost invisible,
and relatively harmless, either way....

Also fix a bug where if a plausible destination directory in CDPATH
was located, but the chdir() failed (eg: permission denied) and then
a later "." or "" CDPATH entry succeeded, "print" mode was turned on.
That is:
cd /tmp; mkdir bin
mkdir -p P/bin; chmod 0 P/bin
CDPATH=/tmp/P:
cd bin
would cd to /tmp/bin (correctly) but print it (incorrectly).

Also when in "cd dest replace" mode, if the result of the replacement
generates '-' as the path named, as in:
cd $PWD -
then simply change to '-' (or attempt to, with CDPATH search), rather
than having this being equivalent to "cd -")

Because of these changes, the pwd command (and $PWD) essentially
always acts as pwd -P, even when called as pwd -L (which is still
the default.)  That is, even more than it did before.

Also fixed a (kind of minor) mem management error (CDPATH related)
"whosoever shall padvance must stunalloc before repeating" (and the
same for MAILPATH).

(kre)

2017-06-04 19:15:46 UTC MAIN commitmail json YAML

Add a 1MB mapping to the MMU init table to cover the FDT blob in case the
bootloader places it beyond the init mem size.

(jmcneill)

2017-06-04 16:35:59 UTC MAIN commitmail json YAML

- prevent optimization from omitting the frame pointer (and re-using it);
  we use it in our inline assembly.
- convert to c a little assembly to make the code more understandable.

(christos)

2017-06-04 15:08:30 UTC MAIN commitmail json YAML

Re-introduce support for multi-block transfers and split transfers to fit
within the 65535-byte limit.

(jmcneill)

2017-06-04 15:00:02 UTC MAIN commitmail json YAML

Give a hint to controllers in the command flags if we are performing a
transfer with an SDHC capable card. If the controller needs to adjust
command args, it can use this hint to understand how it is encoded.

(jmcneill)

2017-06-04 10:58:28 UTC MAIN commitmail json YAML

it's Rorschach, not Rorshach

(mbalmer)

2017-06-04 10:45:50 UTC MAIN commitmail json YAML

Initialise all the SGI/PPI priorities for all CPUs to mask the interrupts

(skrll)

2017-06-04 09:08:06 UTC MAIN commitmail json YAML

Add downlink, uplink, and upload.

(abhinav)

2017-06-04 08:54:38 UTC MAIN commitmail json YAML

2017-06-04 08:53:38 UTC MAIN commitmail json YAML

Fix typo: s/analoguous/analogous/

(abhinav)

2017-06-04 08:52:42 UTC MAIN commitmail json YAML

more dependiences -> dependencies

(mbalmer)

2017-06-04 08:50:27 UTC MAIN commitmail json YAML

fix typo in comment

(mbalmer)

2017-06-04 08:48:05 UTC MAIN commitmail json YAML

Fix typo: s/compatability/compatibility/

(abhinav)

2017-06-04 08:34:34 UTC MAIN commitmail json YAML

2017-06-04 08:05:42 UTC MAIN commitmail json YAML

2017-06-04 08:03:26 UTC MAIN commitmail json YAML

Operations fstrans_start() and fstrans_start_nowait() now always
use FSTRANS_SHARED as lock type so remove the lock type argument.

(hannken)

2017-06-04 08:02:26 UTC MAIN commitmail json YAML

2017-06-04 08:01:33 UTC MAIN commitmail json YAML

Now that FSTRANS is part of VOP_*LOCK() remove FSTRANS and vdead_check()
from genfs_.*lock() and assert the vnode state once the vnode is locked.

(hannken)

2017-06-04 08:00:27 UTC MAIN commitmail json YAML

2017-06-04 07:59:17 UTC MAIN commitmail json YAML

Add "FSTRANS=LOCK" and "FSTRANS=UNLOCK" to vop_lock and vop_unlock.

Add two "static inline" functions to vnode_if.c to handle MPSAFE
and FSTRANS before and after the "VCALL()".

Take FSTRANS and handle error before "VCALL(...vop_lock...)" and
release it after "VCALL(...vop_unlock...)".

(hannken)

2017-06-04 07:58:30 UTC MAIN commitmail json YAML

A vnode is usually called "active", if it has an associated file system
node and a usecount greater zero.  Therefore rename state "VS_ACTIVE"
to "VS_LOADED" and add a new synthetic state "VS_ACTIVE" for VSTATE_ASSERT()
to assert an active vnode.

Add VSTATE_ASSERT_UNLOCKED() to be used with v_interlock unheld and
move the state assertion macros to sys/vnode_impl.h.

(hannken)

2017-06-04 07:18:39 UTC MAIN commitmail json YAML

zero out for 9.0

(snj)

2017-06-04 07:18:22 UTC MAIN commitmail json YAML

roll 8.0 changes into CHANGES.prev

(snj)

2017-06-04 07:17:09 UTC MAIN commitmail json YAML

note netbsd-8

(snj)

2017-06-04 07:16:34 UTC MAIN commitmail json YAML

8.0 update, and add 9.0 for THE FUTURE

(snj)

2017-06-04 07:14:56 UTC MAIN commitmail json YAML

2017-06-04 07:12:09 UTC netbsd-8 commitmail json YAML

2017-06-04 05:37:56 UTC MAIN commitmail json YAML

Fix volume botch.

(nat)

2017-06-03 21:52:05 UTC MAIN commitmail json YAML

DEBUG mode only change.  Convert old trace style to new, and add some more.
NFC for any non-DEBUG shell.

(kre)

2017-06-03 21:32:43 UTC MAIN commitmail json YAML

add __func__ to some panic strings.

(mrg)

2017-06-03 21:31:14 UTC MAIN commitmail json YAML

avoid assert() and simply return errors.

(mrg)

2017-06-03 21:28:48 UTC MAIN commitmail json YAML

2017-06-03 20:55:53 UTC MAIN commitmail json YAML

NFC: Code style only.  Rather than being perverse and adding the
negative of a negative number, just add a positive number instead...
(the previous version came about purely as an accident of the way the
relevant piece of code was added and debugged.... that's my story anyway!)

(kre)

2017-06-03 19:41:14 UTC MAIN commitmail json YAML

Fix typo: s/interrput/interrupt/

(abhinav)

2017-06-03 18:37:37 UTC MAIN commitmail json YAML

The correct usage of recordregion() is (begin, end) not (begin, length).

Fixing this fixes a regression introduced earlier today (UTC) where
arithmetic expressions would be split correctly when the arithmetic
started at the beginning of a word:
echo $(( expression ))
where "begin" is 0, and so (begin, length) is the same as (begin, begin+length)
(aka: (begin,end) - and yes, "end" means 1 after last to consider).
but did not work correctly when the usage was
echo XXX$( expression ))
(begin !+ 0) and would only split (some part of) the result of the expression.

This regression was also foung by the new t_fsplit:split_arith
test case added earlier to the ATF tests for sh.

(kre)

2017-06-03 18:31:35 UTC MAIN commitmail json YAML

When we record an arithmetic expression ($(( ))) as being quoted,
what matters is the quoting state just before we switch into arithmetic
syntax parsing mode, not the state after...

This fixes the regiression introduced earlier today (UTC) where
quoted arithmetic expressions were being subjected to word splitting.

(kre)

2017-06-03 17:54:16 UTC netbsd-7-1 commitmail json YAML

2017-06-03 17:53:59 UTC netbsd-7-0 commitmail json YAML

2017-06-03 17:53:39 UTC netbsd-7 commitmail json YAML

1416, 1421, 1424-1426

(snj)

2017-06-03 17:26:55 UTC netbsd-6 commitmail json YAML

2017-06-03 17:26:42 UTC netbsd-6-1 commitmail json YAML

2017-06-03 17:26:28 UTC netbsd-6-0 commitmail json YAML

2017-06-03 17:24:23 UTC netbsd-6-0 commitmail json YAML

2017-06-03 17:23:36 UTC netbsd-6-0 commitmail json YAML

Pull up following revision(s) (requested by aymeric/christos in ticket #1422):
crypto/external/bsd/openssh/dist/moduli: up to 1.8
Update moduli file.

(snj)

2017-06-03 17:23:17 UTC netbsd-6-1 commitmail json YAML

2017-06-03 17:22:59 UTC netbsd-6-1 commitmail json YAML

Pull up following revision(s) (requested by aymeric/christos in ticket #1422):
crypto/external/bsd/openssh/dist/moduli: up to 1.8
Update moduli file.

(snj)

2017-06-03 17:22:39 UTC netbsd-6 commitmail json YAML

2017-06-03 17:22:26 UTC netbsd-6 commitmail json YAML

Pull up following revision(s) (requested by aymeric/christos in ticket #1422):
crypto/external/bsd/openssh/dist/moduli: up to 1.8
Update moduli file.

(snj)

2017-06-03 17:11:51 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by mbalmer in ticket #1416):
lib/lua/sqlite/sqlite.c: revision 1.9
Guard against double freeing of objects (explicit by the Lua program,
then later by the garbage collector).
This fixes PR bin/52218.

(snj)

2017-06-03 17:05:23 UTC MAIN commitmail json YAML

Add and enable FDT glue for ARM PrimeCell PL050 (KMI) PS2 keyboard/mouse
interface.

(jmcneill)

2017-06-03 17:04:48 UTC netbsd-6 commitmail json YAML

2017-06-03 17:03:36 UTC MAIN commitmail json YAML

Add driver for ARM PrimeCell PL050 (KMI) PS2 keyboard/mouse interface

(jmcneill)

2017-06-03 17:03:02 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by pgoyette in ticket #1421):
sys/dev/usb/files.usb: revision 1.144
Fix the USBVERBOSE stuff so it does not get included in the build if
there are no USB devices or controllers.
Without this change, a kernel with no USB devices but with USBVERBOSE
defined in the configuration file will include the usb_verbose.c file,
but will fail to link due to undefined symbols.

(snj)

2017-06-03 17:01:31 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by skrll in ticket #1424):
sys/arch/arm/arm32/pmap.c: revision 1.345
Perform icache syncs for ARM_MMU_EXTENDED as well.  This helps the PT_STEP
code in pr/52119 and probably other things.

(snj)

2017-06-03 16:58:01 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1425):
sys/kern/kern_descrip.c: revision 1.230
Explicitly set the flags instead of masking set values in.
This fixes FNONBLOCK weirdness seen in audio.c
OK christos@ and martin@.

(snj)

2017-06-03 16:57:17 UTC netbsd-7-1 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1425):
sys/kern/kern_descrip.c: revision 1.230
Explicitly set the flags instead of masking set values in.
This fixes FNONBLOCK weirdness seen in audio.c
OK christos@ and martin@.

(snj)

2017-06-03 16:56:32 UTC netbsd-7-0 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1425):
sys/kern/kern_descrip.c: revision 1.230
Explicitly set the flags instead of masking set values in.
This fixes FNONBLOCK weirdness seen in audio.c
OK christos@ and martin@.

(snj)

2017-06-03 16:55:07 UTC netbsd-7 commitmail json YAML

Pull up following revision(s) (requested by matin in ticket #1426):
sys/arch/i386/stand/misc/rawr32.exe.uue: revision 1.7
Update to rawrite32 1.0.5 (new signatures to avoid scary windows
warnings)

(snj)

2017-06-03 16:54:26 UTC netbsd-7-1 commitmail json YAML

Pull up following revision(s) (requested by matin in ticket #1426):
sys/arch/i386/stand/misc/rawr32.exe.uue: revision 1.7
Update to rawrite32 1.0.5 (new signatures to avoid scary windows
warnings)

(snj)

2017-06-03 16:52:48 UTC netbsd-7-0 commitmail json YAML

Pull up following revision(s) (requested by matin in ticket #1426):
sys/arch/i386/stand/misc/rawr32.exe.uue: revision 1.7
Update to rawrite32 1.0.5 (new signatures to avoid scary windows
warnings)

(snj)

2017-06-03 16:49:29 UTC netbsd-6 commitmail json YAML

Pull up following revision(s) (requested by martin in ticket #1454):
sys/arch/i386/stand/misc/rawr32.exe.uue: revision 1.7
Update to rawrite32 1.0.5 (new signatures to avoid scary windows
warnings)

(snj)

2017-06-03 16:48:41 UTC netbsd-6-1 commitmail json YAML

2017-06-03 16:48:20 UTC netbsd-6-1 commitmail json YAML

Pull up following revision(s) (requested by martin in ticket #1454):
sys/arch/i386/stand/misc/rawr32.exe.uue: revision 1.7
Update to rawrite32 1.0.5 (new signatures to avoid scary windows
warnings)

(snj)

2017-06-03 16:47:51 UTC netbsd-6-0 commitmail json YAML

2017-06-03 16:46:52 UTC netbsd-6-0 commitmail json YAML

Pull up following revision(s) (requested by martin in ticket #1454):
sys/arch/i386/stand/misc/rawr32.exe.uue: revision 1.7
Update to rawrite32 1.0.5 (new signatures to avoid scary windows
warnings)

(snj)

2017-06-03 15:15:49 UTC MAIN commitmail json YAML

Paranoia:  add a new test case testing that $(( )) results get split
by IFS just the same as any other expansion (split when they should be,
and not when they shouldn't).

Good thing I did ... this discovered a regression in the new expand
code (from an hour or three ago) where quoted arith expansions are
being split, and shouldn't be.  (on the other hand, when they should
be split, they are being split correctly, so that's good...)

No need to worry too much about this, in real life (as opposed to
torture tests) no-one ever puts digits in IFS, and a $(( )) expansion
only ever contains digits, so in practice, splitting never happens,
whether because it is quoted, or just becaue there is nothing to split.

The FreeBSD shell does it correctly (they do word splitting using a
totally different mechanism than we do) - I will find where I missed
testing for quoted expansions later tonight.  Until that happens,
expect a test failure from t_fsplit:split_arith

While here add more comments in the other test casess (one had a comment
already) that our shell parses incorrectly (this is a parsing problem,
not an expansion problem, and the bug has existed forever .. and is
shared by bash).

That is, in an expression like "${var:-word}" the whole thing (including
word) is quoted by the double quotes, and in "${var:-"word"}" the
expansion is quoted, but 'word' is not, the 2nd " (the one before 'w')
ends the opening quote, and the third (before }) turns quoting on
again (it is required that there be an even number of unquoted quotes inside
a ${} expression, so things like "${var:-"word} are simply invalid.)
Another way of saying this, is that if the { is quoted (for which the
only way is using " to get to this kind of expansion at all) the }
must also be quoted (" quoted).  There is no quote nesting here.

This also means that in "${var:-'word'}" the single quotes are just
characters, they are quoted by the "" that surround them, just as in
"a 'string' containing quotes", but "${var:-"'word'"}} is valid and
contains a single quoted word.

Note that this is different than the patetrn-match/trim expansions
( ${var%pattern} etc) where any surrounding quotes do not affect the
pattern, and all forms of quoting can be used in it - but it always
parses as a pattern, and is never subject to filename expansion, so
a '*' in it that is to mean "match any string" does not need special
quoting to avoid it expanding to file names, regardless of whether
the ${var%*} is quoted or not, but a * that is to be matched as a
character literally does need to be quoted.

I will probably file a PR about this bug sometime, but as it is
very old, and doesn't every seem to bother anyone (and is shared by
bash) there isn't any big hurry to open yet another verry messy can
of excrement to fix it...

This does mean that the FreeBSD shell "fails" some of our tests.
(The test is wrong, their shell is correct.)

(kre)

2017-06-03 14:51:16 UTC MAIN commitmail json YAML

2017-06-03 14:50:39 UTC MAIN commitmail json YAML

Add driver for ARM PrimeCell Color LCD controller (PL111).

(jmcneill)

2017-06-03 14:49:42 UTC MAIN commitmail json YAML

Add type for ARM PrimeCell PL11x

(jmcneill)

2017-06-03 14:48:03 UTC MAIN commitmail json YAML

2017-06-03 14:47:52 UTC MAIN commitmail json YAML

2017-06-03 14:47:25 UTC MAIN commitmail json YAML

remove my copyright (and clauses 3/4)

(christos)

2017-06-03 14:46:51 UTC MAIN commitmail json YAML

2017-06-03 14:46:29 UTC MAIN commitmail json YAML

2017-06-03 14:45:59 UTC MAIN commitmail json YAML

Complete the special request by quoting chapter & verse from POSIX
as to why ${011} is ${11} and not ${9} (that is, why we interpret it
that way, the "why could it not be the other way?" is just "because
that is not how it was ever implemented".

(kre)

2017-06-03 14:44:12 UTC MAIN commitmail json YAML

2017-06-03 11:51:59 UTC MAIN commitmail json YAML

Adjust the output of {ldr,str}x instructions slightly and deal with the
writeback bit.

(skrll)

2017-06-03 11:23:01 UTC MAIN commitmail json YAML

By special request, add a check that ${011} is ${11} not ${9} (etc) and
that ${08} is not an error.

(kre)

2017-06-03 10:31:16 UTC MAIN commitmail json YAML

Fixes to shell expand (that is, $ stuff) from FreeBSD (implemented
differently...)

In particular ${01} is now $1 not $0  (for ${0any-digits})

${4294967297} is most probably now ""
(unless you have a very large number of params)
it is no longer an alias for $1  (4294967297 & 0xFFFFFFFF) == 1

$(( expr $(( more )) stuff )) is no longer the same as
$(( expr (( more )) stuff )) which was sometimes OK, as in:
$(( 3 + $(( 2 - 1 )) * 3 ))
but not always as in:
$(( 1$((1 + 1))1 ))
which should be 121, but was an arith syntax error as
1((1 + 1))1
is meaningless.

Probably some more.  This also sprinkles a little const, splits a big
func that had 2 (kind of unrelated) purposes into two simpler ones,
and avoids some (semi-dubious) modifications (and restores) in the input
string to insert \0's when they were needed.

(kre)

2017-06-03 10:27:05 UTC MAIN commitmail json YAML

Add some extra sub-tests checking splitting of ${#var} - just for my
piece of mind (to verify I was not breaking anything here.)

Also added some commentary better explaining why one of the tests of splitting
quoted variable expansions is almost certainly incorrect (both the tests,
and what sh does) ... though bash does the same as us, so all is not lost!

(kre)

2017-06-03 09:00:35 UTC MAIN commitmail json YAML

there are no copyright/license statements from "Terrence R. Lambert"
requiring attribution any in our tree any more.

remove it from our list here.

(mrg)