PATCH: new/fixed pcidevs from Attansic, Intel, Ralink

2014-01-06 Thread Alexey E. Suslikov

hi tech@.

(diff is at the bottom of this message).

references used:

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a89534edaaa7008992b878680490e9b02a665563
http://lwn.net/Articles/555179/

Attansic entries being corrected according to above lwn.net reference.

Ralink RT3298 is named Bluetooth to match existing usbdevs practice.

Cheers,
Alexey


OpenBSD 5.4-current (GENERIC.MP) #0: Mon Jan  6 13:51:21 EET 2014
***@***:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4157808640 (3965MB)
avail mem = 4038938624 (3851MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe9d00 (21 entries)
bios0: vendor American Megatrends Inc. version X200CA.203 date 07/11/2013
bios0: ASUSTeK COMPUTER INC. X200CA
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT ECDT MCFG HPET SSDT SSDT SSDT SSDT
acpi0: wakeup devices P0P1(S4) PEG0(S4) PEG1(S4) PEG2(S4) PEG3(S4) 
XHC1(S3) EHC1(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EHC2(S3) USB5(S3) 
USB6(S3) USB7(S3) HDEF(S4) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Pentium(R) CPU 2117U @ 1.80GHz, 1796.21 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Pentium(R) CPU 2117U @ 1.80GHz, 1795.92 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus -1 (PEG0)
acpiprt3 at acpi0: bus -1 (PEG1)
acpiprt4 at acpi0: bus -1 (PEG2)
acpiprt5 at acpi0: bus -1 (PEG3)
acpiprt6 at acpi0: bus 1 (RP01)
acpiprt7 at acpi0: bus -1 (RP03)
acpiprt8 at acpi0: bus -1 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus -1 (RP08)
acpiprt12 at acpi0: bus 2 (RP02)
acpiprt13 at acpi0: bus 3 (RP04)
acpicpu0 at acpi0: C2, C1, PSS
acpicpu1 at acpi0: C2, C1, PSS
acpitz0 at acpi0: critical temperature is 108 degC
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model X200-30 serial   type LIon oem ASUSTeK
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: LCDD
cpu0: Enhanced SpeedStep 1796 MHz: speeds: 1800, 1700, 1600, 1500, 1400, 
1300, 1200, 1100, 1000, 900, 800 MHz

pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 3G Host rev 0x09
vga1 at pci0 dev 2 function 0 Intel HD Graphics 2500 rev 0x09
intagp0 at vga1
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1366x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
Intel 7 Series xHCI rev 0x04 at pci0 dev 20 function 0 not configured
Intel 7 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 Intel 7 Series USB rev 0x04: apic 2 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 Intel 7 Series HD Audio rev 0x04: msi
azalia0: codecs: Conexant/0x510f, Intel/0x2806, using Conexant/0x510f
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 7 Series PCIE rev 0xc4: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 Intel 7 Series PCIE rev 0xc4: msi
pci2 at ppb1 bus 2
Ralink RT3290 rev 0x00 at pci2 dev 0 function 0 not configured
Ralink Bluetooth rev 0x00 at pci2 dev 0 function 1 not configured
ppb2 at pci0 dev 28 function 3 Intel 7 Series PCIE rev 0xc4: msi
pci3 at ppb2 bus 3
Attansic Technology AR8172 rev 0x10 at pci3 dev 0 function 0 not 
configured

ehci1 at pci0 dev 29 function 0 Intel 7 Series USB rev 0x04: apic 2 int 23
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 Intel HM70 LPC rev 0x04
pciide0 at pci0 dev 31 function 2 Intel 7 Series SATA rev 0x04: DMA, 
channel 0 configured to native-PCI, channel 1 configured to native-PCI

pciide0: using apic 2 int 19 for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: 

PATCH: new usbdevs vendor Sunplus, new wi-fi devices

2014-01-06 Thread Alexey E. Suslikov

hi tech@.

references used:

http://svnweb.freebsd.org/base?view=revisionrevision=238779
http://svnweb.freebsd.org/base?view=revisionrevision=257955

Cheers,
Alexey


Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x), 
Intel(0x8086), rev 1.00
 port 1 addr 2: high speed, self powered, config 1, Rate Matching 
Hub(0x0024), Intel(0x8087), rev 0.00

  port 1 powered
  port 2 powered
  port 3 powered
  port 4 powered
 port 2 powered
Controller /dev/usb1:
addr 1: high speed, self powered, config 1, EHCI root hub(0x), 
Intel(0x8086), rev 1.00
 port 1 addr 2: high speed, self powered, config 1, Rate Matching 
Hub(0x0024), Intel(0x8087), rev 0.00
  port 1 addr 6: high speed, power 450 mA, config 1, 11n 
Adapter(0x3c15), D-Link(0x2001), rev 1.01, iSerialNumber 1.0
  port 2 addr 3: low speed, power 46 mA, config 1, 2.4GHz 2way RF 
Receiver(0x053a), Sunplus Innovation Technology Inc.(0x1bcf), rev a0.51

  port 3 powered
  port 4 addr 5: high speed, power 500 mA, config 1, USB2.0 HD UVC 
WebCam(0x5603), Generic(0x0bda), rev 5.30, iSerialNumber 0x0001

 port 2 powered


Index: usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.618
diff -u -p -r1.618 usbdevs
--- usbdevs 17 Dec 2013 12:51:14 -  1.618
+++ usbdevs 6 Jan 2014 13:27:13 -
@@ -585,6 +585,7 @@ vendor TML  0x1b91  The Mobility Lab
 vendor TCTMOBILE   0x1bbb  TCT Mobile
 vendor MDS 0x1bc8  MDS
 vendor ALTI2   0x1bc9  Alti-2
+vendor SUNPLUS 0x1bcf  Sunplus Innovation Technology Inc.
 vendor WAGO0x1be3  WAGO Kontakttechnik
 vendor LONGCHEER   0x1c9e  Longcheer Technology
 vendor DRESDENELEC 0x1cf1  Dresden Elektronic
@@ -1463,6 +1464,7 @@ product DLINK RT2570  0x3c00  RT2570
 product DLINK DUBE100B10x3c05  DUB-E100 rev B1
 product DLINK RT2870   0x3c09  RT2870
 product DLINK RT3072   0x3c0a  RT3072
+product DLINK DWA140B3 0x3c15  DWA-140 rev B3
 product DLINK DWA127   0x3c1b  DWA-127
 product DLINK DSB650C  0x4000  10Mbps Ethernet
 product DLINK DSB650TX10x4001  10/100 Ethernet
@@ -3390,6 +3392,7 @@ product RALINK RT3071 0x3071  RT3071
 product RALINK RT3072  0x3072  RT3072
 product RALINK RT3370  0x3370  RT3370
 product RALINK RT3572  0x3572  RT3572
+product RALINK RT5370  0x5370  RT5370
 product RALINK RT8070  0x8070  RT8070
 product RALINK RT2570_30x9020  RT2570
 product RALINK RT2573_20x9021  RT2573



Re: PATCH: new usbdevs vendor Sunplus, new wi-fi devices

2014-01-06 Thread Alexey E. Suslikov
previous diff may be mangled. resending.

Index: usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.618
diff -u -p -r1.618 usbdevs
--- usbdevs 17 Dec 2013 12:51:14 -  1.618
+++ usbdevs 6 Jan 2014 13:27:13 -
@@ -585,6 +585,7 @@ vendor TML  0x1b91  The Mobility Lab
 vendor TCTMOBILE   0x1bbb  TCT Mobile
 vendor MDS 0x1bc8  MDS
 vendor ALTI2   0x1bc9  Alti-2
+vendor SUNPLUS 0x1bcf  Sunplus Innovation Technology Inc.
 vendor WAGO0x1be3  WAGO Kontakttechnik
 vendor LONGCHEER   0x1c9e  Longcheer Technology
 vendor DRESDENELEC 0x1cf1  Dresden Elektronic
@@ -1463,6 +1464,7 @@ product DLINK RT2570  0x3c00  RT2570
 product DLINK DUBE100B10x3c05  DUB-E100 rev B1
 product DLINK RT2870   0x3c09  RT2870
 product DLINK RT3072   0x3c0a  RT3072
+product DLINK DWA140B3 0x3c15  DWA-140 rev B3
 product DLINK DWA127   0x3c1b  DWA-127
 product DLINK DSB650C  0x4000  10Mbps Ethernet
 product DLINK DSB650TX10x4001  10/100 Ethernet
@@ -3390,6 +3392,7 @@ product RALINK RT3071 0x3071  RT3071
 product RALINK RT3072  0x3072  RT3072
 product RALINK RT3370  0x3370  RT3370
 product RALINK RT3572  0x3572  RT3572
+product RALINK RT5370  0x5370  RT5370
 product RALINK RT8070  0x8070  RT8070
 product RALINK RT2570_30x9020  RT2570
 product RALINK RT2573_20x9021  RT2573



Re: PATCH: new/fixed pcidevs from Attansic, Intel, Ralink

2014-01-06 Thread Alexey E. Suslikov
previous diff may be mangled. resending.

Index: sys/dev/pci/pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1708
diff -u -p -r1.1708 pcidevs
--- sys/dev/pci/pcidevs 5 Jan 2014 23:55:25 -   1.1708
+++ sys/dev/pci/pcidevs 6 Jan 2014 13:46:04 -
@@ -1848,8 +1848,10 @@ product ATTANSIC L2C 0x1062  L2C
 product ATTANSIC L1C   0x1063  L1C
 product ATTANSIC L1D   0x1073  L1D
 product ATTANSIC L1D_1 0x1083  L1D
-product ATTANSIC L2F   0x1090  L2F
-product ATTANSIC L1F   0x1091  L1F
+product ATTANSIC L2F   0x1090  AR8162
+product ATTANSIC L1F   0x1091  AR8161
+product ATTANSIC L2F_1 0x10a0  AR8172
+product ATTANSIC L1F_1 0x10a1  AR8171
 product ATTANSIC L20x2048  L2
 product ATTANSIC L2C_1 0x2060  L2C
 product ATTANSIC L2C_2 0x2062  L2C
@@ -3197,6 +3199,7 @@ product INTEL 7SERIES_RAID_1  0x1e04  7 Se
 product INTEL 7SERIES_RAID_2   0x1e06  7 Series RAID
 product INTEL 7SERIES_RAID_3   0x1e07  7 Series RAID
 productINTEL 7SERIES_SATA_30x1e08  7 Series SATA
+productINTEL 7SERIES_SATA_40x1e09  7 Series SATA
 product INTEL 7SERIES_RAID_4   0x1e0e  7 Series RAID
 product INTEL 7SERIES_PCIE_1   0x1e10  7 Series PCIE
 product INTEL 7SERIES_PCIE_2   0x1e12  7 Series PCIE
@@ -5615,6 +5618,8 @@ product RALINK RT3062 0x3062  RT3062
 product RALINK RT3090  0x3090  RT3090
 product RALINK RT3091  0x3091  RT3091
 product RALINK RT3092  0x3092  RT3092
+product RALINK RT3290  0x3290  RT3290
+product RALINK RT3298  0x3298  Bluetooth
 product RALINK RT3562  0x3562  RT3562
 product RALINK RT3592  0x3592  RT3592
 product RALINK RT3593  0x3593  RT3593



Re: Randomization from the bootblocks

2014-01-03 Thread Alexey E. Suslikov
Theo de Raadt deraadt at cvs.openbsd.org writes:

 Having no interrupt (and such) entropy means less entropy.
 
 From other hand, there are lot of speculations about some
 hardware entropy sources are suspected (proven?) bad (or
 intentionally hijacked?).
 
 So question here is, does moving random generation closer
 to hardware paves a way to more predictable numbers?
 
 It is clear you don't understand the code that was commited.

You're right. Now I see: the code in question tries to XOR
*over* hardware randomness.



Re: Weird loop in ftp client

2013-11-23 Thread Alexey E. Suslikov
sven falempin sven.falempin at gmail.com writes:

 
 Hello,
 
 Another point of vue :
 Because curl is in base, what does ftp client add to the system ?

pkg_delete curl and you'll understand.



Re: new queue support for systat(1)

2013-11-21 Thread Alexey E. Suslikov
Arto Jonsson ajonsson at kapsi.fi writes:

 the following adds new queue support for systat(1). Both old and new
 queues are shown in the same display (newqs are shown first). Majority
 of the code taken from pfctl.

I would love to see prio support too :)



Re: FDDI/ATM leftovers

2013-11-18 Thread Alexey E. Suslikov
Martin Pieuchot mpieuchot at nolizard.org writes:

 - case IFT_FDDI:
 - case IFT_ATM:
   case IFT_IEEE1394:

any plans for FireWire? :)



Re: Don't link multicast records to the first address

2013-11-18 Thread Alexey E. Suslikov
Martin Pieuchot mpieuchot at nolizard.org writes:

  at  at  -1803,8 +1651,12  at  at  in6_delmulti(struct in6_multi
*in6m)

snip

 + s = splsoftnet();
 + TAILQ_REMOVE(ifp-if_maddrlist, in6m-in6m_ifma, ifma_list);
 + splx(s);
 +
   free(in6m, M_IPMADDR);
   }
   splx(s);

this splx seems wrong.



Re: rfc: acpi wmi diff

2013-11-17 Thread Alexey E. Suslikov
Kyle R W Milz kyle at getaddrinfo.net writes:

 
 tech at ,
 
 Here is an initial implementation of a generic acpi wmi framework and a
 single consumer for the framework that lets the volume adjustment keys
 on an asus ux31e work.
 
 The generic framework could be used to support hotkeys found in
 different acer, dell, hp, msi, other laptops.
 
 This is by no means complete as wmi can do all sorts of other stupid
 things like blink leds, toggle radios, control backlights, etc. The code
 has some style(9) issues.
 
 Looking for feedback before I go any further.
 
 Index: arch/amd64/conf/GENERIC
 ===
 RCS file: /cvs/src/sys/arch/amd64/conf/GENERIC,v
 retrieving revision 1.352
 diff -u -p -r1.352 GENERIC
 --- arch/amd64/conf/GENERIC   4 Nov 2013 14:07:15 -   1.352
 +++ arch/amd64/conf/GENERIC   17 Nov 2013 05:53:40 -
  at  at  -58,6 +58,8  at  at  acpitoshiba*at acpi?
  acpivideo*   at acpi?
  acpivout*at acpivideo?
  acpipwrres*  at acpi?
 +acpiwmi* at acpi?
 +acpiwmi_asus*at acpiwmi?

afaik, using underscore in device name is against OpenBSD conventions.

also, if WMI maybe used to implement different vendors' features, would
it be useful to use

acpiwmi* at acpi?
wmiasus* at acpiwmi?

model to have common WMI abstraction under acpiwmi and vendor-specific
stuff under wmivendor (like acpi(4) and acpiasus(4) for instance)?



5.4 html Security Improvements section

2013-10-09 Thread Alexey E. Suslikov
hi tech@.

Security Improvements section needs love.

I have found these:

* rand(3)/random(3) - arc4random*() conversion
* new secure identd implementation (not started by default)
* security(8) now checks npppd(8) configuration files

More?



Re: 5.4 html Security Improvements section

2013-10-09 Thread Alexey E. Suslikov
Alexey E. Suslikov alexey.suslikov at gmail.com writes:

 
 hi tech at .
 
 Security Improvements section needs love.
 
 I have found these:
 
 * rand(3)/random(3) - arc4random*() conversion
 * new secure identd implementation (not started by default)
 * security(8) now checks npppd(8) configuration files

* more random(4) randomness from dmesg, disklabel checksum and
manufacturer-supplied bios serial/uuid;
* Added AES-XTS support to aesni crypto(4) driver on amd64.
Allows softraid(4) to benefit from the AES-NI instructions on
newer Intel CPUs
* Switched the malloc(3) and pool freelists to using xor
simpleq. Adds a tiny bit more protection from list manipulation.




Re: OpenBSD on a Nokia IP380

2013-08-28 Thread Alexey E. Suslikov
 s_gammons at charter.net writes:

 installed.  Guess I'll have to live with the 4 onboard NICs for the time 
 being.

If you have no plans to forward full-blown 100Mbps between fxps
and there's a dot1q-aware switch near you, using vlans may be a
workaround for a limited number of physical ports.



viomb(4) assert with 1.35 of sys/arch/amd64/amd64/intr.c

2013-07-01 Thread Alexey E. Suslikov
Hi ports@.

See here http://article.gmane.org/gmane.os.openbsd.misc/205448

In addition, viomb_worker is doing splvm() and workq itself is

viomb_workq = workq_create(viomb, 1, IPL_VM);

Cheers,
Alexey



Re: sysctl fix

2013-06-06 Thread Alexey E. Suslikov
Sylvestre Gallon ccna.syl at gmail.com writes:

  at  at  -2586,6 +2587,7  at  at  struct emulname {
  } *emul_names;
  int  emul_num, nemuls;
  int  emul_init(void);
 +int  emulcmp(const void *, const void *);

this seems unrelated to rest of changes you've made. no?



Re: Stop printing excessive numbers of ACPI wakeup devices

2013-06-01 Thread Alexey E. Suslikov
Mike Larkin mlarkin at azathoth.net writes:

 It's sometimes nice to know what devices can wake up a machine, and from what
 sleep state. But I'm fine suppressing these also. Don't want this to end up
 being a bikeshed :)

why not dnprintf them?



Re: pf state tracking and tos/dscp

2013-05-23 Thread Alexey E. Suslikov
Adam Gensler openbsd at kristenandadam.net writes:

 all udp 1.1.1.1:4500 - 172.28.1.3:4500   MULTIPLE:MULTIPLE
   age 00:15:50, expires in 00:00:57, 394:196 pkts, 52356:39176 bytes, rule 37

put pass all tos  higher in your ruleset and see if it matches.



Re: pf state tracking and tos/dscp

2013-05-23 Thread Alexey E. Suslikov
Adam Gensler openbsd at kristenandadam.net writes:

 local_nets = { 172.28.1.0/24, 172.28.10.0/24, 172.28.11.0/24 }
 work871 = 172.28.1.3
 pass in quick inet proto udp from $work871 tos 0xB8 tag VOIP-RTP
 pass in quick inet proto udp from $work871 tos 0x60 tag VOIP-SIG
 pass in quick inet proto { tcp, udp } from $local_nets

Another possible thing I see, is a tunnel originating side.

Since tos rules you have are unidirectional (in terms of match),
they will create state if only first packet comes from $work871.

However, first packet coming from other side will match another
rule and create state, so all subsequent tunnel's packets will
not hit tos rules.



De-static functions' prototypes

2013-05-21 Thread Alexey E. Suslikov
 CVSROOT:  /cvs
 Module name:  src
 Changes by:   kettenis at cvs.openbsd.org   2013/05/20 11:34:08

 Modified files:
   sys/arch/i386/i386: amd64errata.c 
   sys/arch/amd64/amd64: amd64errata.c 

 Log message:
 de-static-ize, such that people don't get confused by aesni failures on
 AMD hardware the next time somebody tries to run on a broken KVM hypervisor.

unfortunately, it still confuses with aesni failures.

de-static-izing functions' prototypes makes things look
as expected.

Index: arch/amd64/amd64/amd64errata.c
===
RCS file: /cvs/src/sys/arch/amd64/amd64/amd64errata.c,v
retrieving revision 1.4
diff -u -p -u -p -r1.4 amd64errata.c
--- arch/amd64/amd64/amd64errata.c  20 May 2013 17:34:08 -  1.4
+++ arch/amd64/amd64/amd64errata.c  20 May 2013 20:17:00 -
@@ -129,8 +129,8 @@ static const uint8_t amd64_errata_set9[]
DA_C3, HY_D0, HY_D1, HY_D1_G34R1,  PH_E0, LN_B0, OINK
 };
 
-static int amd64_errata_setmsr(struct cpu_info *, errata_t *);
-static int amd64_errata_testmsr(struct cpu_info *, errata_t *);
+int amd64_errata_setmsr(struct cpu_info *, errata_t *);
+int amd64_errata_testmsr(struct cpu_info *, errata_t *);
 
 static errata_t errata[] = {
/*
Index: arch/i386/i386/amd64errata.c
===
RCS file: /cvs/src/sys/arch/i386/i386/amd64errata.c,v
retrieving revision 1.4
diff -u -p -u -p -r1.4 amd64errata.c
--- arch/i386/i386/amd64errata.c20 May 2013 17:34:08 -  1.4
+++ arch/i386/i386/amd64errata.c20 May 2013 20:17:01 -
@@ -129,8 +129,8 @@ static const uint8_t amd64_errata_set9[]
DA_C3, HY_D0, HY_D1, HY_D1_G34R1,  PH_E0, LN_B0, OINK
 };
 
-static int amd64_errata_setmsr(struct cpu_info *, errata_t *);
-static int amd64_errata_testmsr(struct cpu_info *, errata_t *);
+int amd64_errata_setmsr(struct cpu_info *, errata_t *);
+int amd64_errata_testmsr(struct cpu_info *, errata_t *);
 
 static errata_t errata[] = {
/*




Re: cvsweb says 'No viewable change' for i915_drv.c diffs

2013-05-15 Thread Alexey E. Suslikov
Mark Kettenis mark.kettenis at xs4all.nl writes:

  Try this
 
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/drm/i915/i915_drv.c.diff?r1=1.26;r2=1.27;f=h
  
  and, for instance, this
 
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/drm/i915/i915_dma.c.diff?r1=1.6;r2=1.7;f=h
  
  Former says No viewable change. I think it isn't normal. Am I wrong?
 
 Yes that's very annoying.  I suspect cvsweb has problems with the UTF8
 characters in the copyright header.

cvsweb operates on individual diff chunks while preparing
viewable output, right?

if so, and you are right about UTF8, only one of these chunks
is a showstopper.

maybe cvsweb may say No viewable change for a problematic
chunk only, instead of completely freaking out.



Re: DPI for pf(4)

2013-04-30 Thread Alexey E. Suslikov
Franco Fichtner slashy83 at gmail.com writes:

 so I have been working on a BSD licensed DPI engine.  It's a
 very lightweight, non-intrusive approach and I know that teasers
 are boring, but I'd like to know if it's worth the time to
 work on inclusion for pf(4).  So far I have about 25 supported
 applications and the necessary hooks for the pf.conf(5) parts.

If DPI stands for Deep Packet Inspection, than (afaik)
it was discussed before: this kind of inspection is too
complex to put into a kernel.

relayd already supports L7 filtering at least for http,
so if something is to be improved in this area, relayd
is better place, imo.



Re: beaglebone

2013-04-25 Thread Alexey E. Suslikov
Raphael Graf r at undefined.ch writes:

 I have a beaglebone (AM3359) running OpenBSD, see below.
 Is there any interest in such code?

Diffs are interesting. Teasers are not.



Re: goodbye to some isa devices

2013-03-28 Thread Alexey E. Suslikov
Nick Holland nick at holland-consulting.net writes:

 There is a lot of ISA stuff I'd object to removing from the kernel; none
 of this is it.  I'm entirely ok with this stuff going...

How about this one?

ie0 at isa? port 0x360 iomem 0xd irq 7  # StarLAN and 3C507

Looking at sys/dev/isa/if_ie.c shows different pieces of
code glued together and it is relative big (~2000 LOC).



Re: goodbye to some isa devices

2013-03-26 Thread Alexey E. Suslikov
Todd T. Fries todd at fries.net writes:

 I'd wager a bet that I could make my sea(4) scsi adapter work more
 reliably than any variant of usb wi(4), so perhaps we should disable usb
 wi(4) to save you time building instead?

My 2 cents.

Nuke tcic0 *and* pcic*:
* searching archives bring dmesgs from 3.x/4.x era,
* how big chances are to run 5.x on laptops with these
PCMCIA controllers?

Not sure about ancient 3Com's, but they are Ethernet at
least, in contract to Token-Ring device like tr*.

Do we support Token-Ring?

Cheers,
Alexey



Re: goodbye to some isa devices

2013-03-26 Thread Alexey E. Suslikov
Alexey E. Suslikov alexey.suslikov at gmail.com writes:

 Not sure about ancient 3Com's, but they are Ethernet at
 least, in contract to Token-Ring device like tr*.
 
 Do we support Token-Ring?

Joystick driver?



Re: softraid(4) about boot support

2013-03-11 Thread Alexey E. Suslikov
Alexander Polakov plhk at sdf.org writes:

 It seems like this is not true any more. Right?
 
 Index: softraid.4

snip

 -There is no boot support at this time for any disciplines.
 -.Pp

Not telling RAID1 and CRYPTO are only bootable disciplines,
won't make truth either.



Re: raid10 for softraid(4)

2013-02-21 Thread Alexey E. Suslikov
Dmitry Bogdan dmitry.bogdan at gmail.com writes:

 Is there any interest in the raid10 independent discipline
 in openbsd community?

With hardware based RAID-controllers our company
prefer RAID10 for better write speeds (because
RAID5 needs parity calculations, for instance).

We also use softraid(4) mirroring a lot. And, yes,
having RAID10 with softraid(4) would be nice.

We'll be checking tech@ for your diffs ;) and will
be glad to test them.

Cheers,
Alexey



Re: Add ATI Radeon HD 7850 and 7850 HD Audio to pcidevs

2013-01-13 Thread Alexey E. Suslikov
Thomas Pfaff tpfaff at tp76.info writes:

  product ATI RADEON_HD6400_HDA0xaa98  Radeon HD 6400 Audio
 +product ATI RADEON_HD7850_HDA0xaab0  Radeon HD 7850 HD Audio

I think 7850 audio entry shouldn't say HD twice (see 6400).



Re: upstream vendors and why they can be really harmful

2012-11-09 Thread Alexey E. Suslikov
sickmind at lavabit.com writes:
 As far as I know they are going to release their own linux distro
 called GNOME OS with it's own API (GNOME API) and stuff. In this case
 making GNOME incompatible with everything else and all that talk about
 brands and marketing both make sense.

From https://trac.transmissionbt.com/ticket/3685#comment:4


I guess you have to decide if you are a GNOME app, an Ubuntu app,
or an XFCE app unfortunately. I'm sorry that this is the case but
it wasn't GNOME's fault that Ubuntu has started this fork. And I
have no idea what XFCE is or does sorry.

It is my hope that you are a GNOME app. Yes this kind of
fragmentation is unfortunate. I'm not happy about it either.
Anyway, I just wanted to give you a heads up. Wish you the best.


How dirty! If you assume XFCE can have an app, you sure know what
XFCE is!

Isn't it a hypocrisy that GNOME people trade fragmentation in one
hand and be-my-app salvation in another with all-understanding
faces?

Let's be straight:
* Not a GNOME app? You will be unable to use notification area.
* Not a systemd app? You will be unable to run at all.

In other words you either an app, or dead one.

What I see here is GNOME and Ubuntu building their own sandboxes,
like Apple Store, Android Market, Ovi Store, name it. So first of
all they need to turn portable applications into not-so-portable
apps.

This effectively means open source software placed into a sandbox
under single App Store EULA.

Another interesting thing is Zuck condemned HTML5 (another way to
build portable applications) in favor of native apps.

No doubts FacePhones and FacePads will have native Facebook Apps.

Cheers,
Alexey



Re: Use ACPI to detect secondary PCI root segments on x86

2012-09-14 Thread Alexey E. Suslikov
Christian Ehrhardt ehrhardt at genua.de writes: 
  However, host bridges that are handled e.g. in arch/i386/pci/pchb.c
  can appear downstream of another bridge but use bus numbers that are
  outside of the upstream bridge's bus number range.

What I understood from the discussion, there is a possibility
of kinda multi-path within pci discovery. Right?

No being a pci guru, I did some work on azalia(4) in the past.

azalia(4) also need to deal with multi-path, but for signal
flow: audio codec has numerous one-to-one, one-to-many or
many-to-many connected nodes (dacs, adcs, mixers) which
signal should pass through.

Some signal paths are dead-end, some aren't.

azalia(4) uses so called traversing mechanism do detect
right signal flow and mark dead nodes as dead. So the result
of traversing is a tree-like structure (I'm simplifying here)
containing right signal path.

That's the principle: do traverse first, than operate.

pci bus structure is also tree-like and maybe it is better
to do traversing first, remove duplicated nodes and than do
actual device attachments.

Doing traversing may involve different bus discovery methods
(bios, acpi etc).

Just a raw idea.



KERNEL MODIFICATION in config(8)

2012-03-21 Thread Alexey E. Suslikov
Hello tech@.

In KERNEL MODIFICATION section:

...
 When invoked, the kernel identification is first shown.

   # config -e -o bsd.new /bsd
   OpenBSD 2.6-beta (GENERIC.rz0) #0: Mon Oct  4 03:57:22 MEST 1999
   root@winona:/usr/src/sys/arch/pmax/compile/GENERIC.rz0
   Enter 'help' for information
   ukc

 One or more warnings may be printed before the ukc prompt.

   warning: no output file specified

 Neither the -f nor -o option has been specified.  Changes will be
 ignored.

   WARNING this kernel doesn't contain all information needed!
   WARNING the commands add and change might not work.

 The kernel is too old (pre OpenBSD 2.6) and cannot support all of the
 functionality needed by the -e option.

   WARNING kernel mismatch. -u ignored.
   WARNING the running kernel version:
...

Isn't that OpenBSD 2.6-beta pmap arch config example somewhat exotic and 
outdated? So about too old pre OpenBSD 2.6 kernel comment.

If above is done on purpose, just curious about the purpose :)

Alexey



Re: Proxy ARP, but network interface specific

2012-01-23 Thread Alexey E. Suslikov
Gerlach, Hendrik hendrik.gerlach at siemens.com writes:

 In opposite to Linux it seems to be impossible in OpenBSD to add proxy ARP
 entries only for a specific network interface (missing option for the ARP
 command) nor to disable proxy ARP at all for some interfaces (sysctl or
 ifconfig option).
 
 So it seems that some code change is necessary. Are there some solutions,
 hints or papers or some ideas that could help us ?

You can try to cook something using vether(4) and bridge(4).

Alexey




Re: enable aucat by default

2011-10-07 Thread Alexey E. Suslikov
Jona Joachim jaj at hcl-club.lu writes:

 
 On 2011-10-07, Henning Brauer lists-openbsdtech at bsws.de wrote:
  * Jona Joachim jaj at hcl-club.lu [2011-10-07 12:06]:
  Do you want to start sshd by default? [Y/n]
  Do you want to start aucat by default? [Y/n]
 
  yeah right. what an awesome installer!
 
  Do you want to start atactl by default? [Y/n]
 [snip silly for-loop on /usr/bin]
 
 The installer asks about X11 and sshd because whether you start them or
 not is largely based on whether you plan to run a server or a desktop
 system.
 aucat is similar to X11 in this regard: necessary for a desktop, useless
 on a server.

Either audioctl or mixerctl, which both return Device not configured if no
audio device is present, can be used by aucat rc.d script to detect speechless
setups.

Alexey



Re: enable aucat by default

2011-10-07 Thread Alexey E. Suslikov
Vadim Zhukov persgray at gmail.com writes:

 
 2011/10/7 Alexey E. Suslikov alexey.suslikov at gmail.com:
  Either audioctl or mixerctl, which both return Device not configured
  if no audio device is present, can be used by aucat rc.d script to
  detect speechless setups.
 
 Still will not work for uaudio(4) case... some default rules for hotplugd?

1st: aucat can't be run with audio device detached and wait it to become
attached. 2nd: hotplugd have no dedicated class for audio. 3rd: you will
need to run hotplugd by default too.

From my understanding, making aucat a default won't make *every* of audio
setups around happy, but, as noted above, will do magic in proper way for
*most* of them.

Alexey



Re: enable aucat by default

2011-10-07 Thread Alexey E. Suslikov
Theo de Raadt deraadt at cvs.openbsd.org writes:

 
  Either audioctl or mixerctl, which both return Device not configured if
  no audio device is present, can be used by aucat rc.d script to detect
  speechless setups.
 
 Until a hotplug one is put in, and doesn't work.

Is it feasible for aucat to act like hotplugd but for audio devices?

According to hotplugd source, it's fairly trivial /dev/hotplug event
reading loop.