In message: <[EMAIL PROTECTED]>
Gary Palmer <[EMAIL PROTECTED]> writes:
: M. Warner Losh wrote:
:
: >This works. However, matches should already be case insensitive. If
: >they aren't, then I need to investigate why not.
: >
: >
:
: My reading of regex(3) says that the reg_comp at
M. Warner Losh wrote:
This works. However, matches should already be case insensitive. If
they aren't, then I need to investigate why not.
My reading of regex(3) says that the reg_comp at line 173 of devd.cc
needs to add the REG_ICASE flag. i.e.
regcomp(&_regex, _re.c_str(), RE
In message: <[EMAIL PROTECTED]>
Gary Palmer <[EMAIL PROTECTED]> writes:
: Sam Leffler wrote:
:
: > At one point I added shorthand logic in devd for things like vendor,
: > device, subvendor, etc. that did numeric comparisons instead of
: > regex's. It might be worthwhile to extend t
Sam Leffler wrote:
At one point I added shorthand logic in devd for things like vendor,
device, subvendor, etc. that did numeric comparisons instead of
regex's. It might be worthwhile to extend the grammar to have a
numeric match operator.
Something like the attached patch? It seems to wo
Gary Palmer wrote:
Hi Warner,
I've been playing with devd and noticed that if you do something like:
#
# Dell TrueMobile 1300 WLAN PC Card
#
nomatch 10 {
match "bus" "pci[0-9]+";
match "vendor" "0x14E4";
match "device" "0x4320";
match "subvendor" "0x1028";
mat
Hi Warner,
I've been playing with devd and noticed that if you do something like:
#
# Dell TrueMobile 1300 WLAN PC Card
#
nomatch 10 {
match "bus" "pci[0-9]+";
match "vendor" "0x14E4";
match "device" "0x4320";
match "subvendor" "0x1028";
match "subdevice" "0x00
