On Fri, Oct 07, 2022 at 01:44:50PM -0700, Mike Larkin wrote:
> On Fri, Oct 07, 2022 at 11:59:49AM -0700, Bryan Vyhmeister wrote:
> > Hey Patrick,
> >
> > I hope you're doing well. We have not talked in quite a while. I was
> > wondering how well the support for the
Hey Patrick,
I hope you're doing well. We have not talked in quite a while. I was
wondering how well the support for the ThinkPad X13s works right now in
OpenBSD. I did some searching around and couldn't find much other than
"support being added" but I'm not sure if that means everything works or
On Wed, Aug 11, 2021 at 03:44:33PM +0200, Ingo Schwarze wrote:
> Hi,
>
> > ok gerhard@
>
> Thanks for reporting, for the initial patch, and for checking the
> final one. This now committed.
>
> Yours,
> Ingo
Thanks to all for working together and getting this fixed.
Bryan
On Thu, Dec 10, 2020 at 10:03:16PM -0800, Bryan Vyhmeister wrote:
> On Mon, Nov 30, 2020 at 07:58:39AM -0800, Bryan Vyhmeister wrote:
> > On Mon, Oct 19, 2020 at 08:11:04PM -0700, Bryan Vyhmeister wrote:
> > > On Fri, Oct 02, 2020 at 12:33:15PM -0700, Bryan Vyhmeister wrote:
>
On Mon, Nov 30, 2020 at 07:58:39AM -0800, Bryan Vyhmeister wrote:
> On Mon, Oct 19, 2020 at 08:11:04PM -0700, Bryan Vyhmeister wrote:
> > On Fri, Oct 02, 2020 at 12:33:15PM -0700, Bryan Vyhmeister wrote:
> > > On Wed, Sep 30, 2020 at 04:05:51PM -0700, Bryan Vyhmeister wrote:
&g
On Mon, Oct 19, 2020 at 08:11:04PM -0700, Bryan Vyhmeister wrote:
> On Fri, Oct 02, 2020 at 12:33:15PM -0700, Bryan Vyhmeister wrote:
> > On Wed, Sep 30, 2020 at 04:05:51PM -0700, Bryan Vyhmeister wrote:
> > > Gerhard Roth provided a patch to me to get the Qualcomm Snapdrag
On Fri, Oct 02, 2020 at 12:33:15PM -0700, Bryan Vyhmeister wrote:
> On Wed, Sep 30, 2020 at 04:05:51PM -0700, Bryan Vyhmeister wrote:
> > Gerhard Roth provided a patch to me to get the Qualcomm Snapdragon X20
> > umb(4) interface in my Dell Latitude 7300 working. It is also know
On Wed, Sep 30, 2020 at 04:05:51PM -0700, Bryan Vyhmeister wrote:
> Gerhard Roth provided a patch to me to get the Qualcomm Snapdragon X20
> umb(4) interface in my Dell Latitude 7300 working. It is also known as a
> Dell DW5821e interface. I have been using this patch for months now wi
Gerhard Roth provided a patch to me to get the Qualcomm Snapdragon X20
umb(4) interface in my Dell Latitude 7300 working. It is also known as a
Dell DW5821e interface. I have been using this patch for months now with
AT&T Wireless in the US and it works great just as I have been used to
on my Think
I just purchased a Dell Latitude 7300 which I ordered with a Dell
DW5821e Snapdragon X20 LTE device. Attached is a patch to add it to
usbdevs. I am working on getting it to work with umb(4) but this is a
needed step as I understand it. Also attached is my usbdevs output for
this device. Thank you.
On Sat, Nov 16, 2019 at 10:01:44PM -0800, Philip Guenther wrote:
> Looking good so far on my X1 extreme once I
> added PCI_PRODUCT_INTEL_WL_9560_2 next to the _1 lines in if_iwm.c.
> Awesome!
Could this change be committed as well? This allows the 9560 on my
ThinkPad P1 to work as well. Thank you!
On Tue, Aug 14, 2018 at 05:53:43PM +0300, Denis wrote:
> Most of modern modems have serial discipline ports and USB Mobile
> Broadband Interface Model (MBIM) interface in some port compositions
> simultaneously. It seems very useful to have different disciplines
> supported by umsm(4) and umb(4) dr
On Wed, Jul 25, 2018 at 02:30:19PM +0100, Stuart Henderson wrote:
> The problem is that if the clock is wrong, the server's certificate
> and/or OCSP stapling can't be validated (it either appears to have
> expired, or not be valid yet), so ntpd is unable to connect using https
> to check the time.
On Wed, Jul 25, 2018 at 08:51:53AM +0100, Stuart Henderson wrote:
> On 2018/07/24 13:25, Bryan Vyhmeister wrote:
> > (Obviously clock was wrong and I did not realize it. Looks like ntpd is
> > not setting the clock with -s for some reason so rdate did the trick.)
>
> If the
Do we want the WD Black NVMe identified or should we just leave it out?
Also, if you want the SSD to not be identified, should at least the
vendor be added? Thanks again.
Bryan
Index: sys/dev/pci/pcidevs
===
RCS file: /cvs/src/sys/d
On Mon, Jul 23, 2018 at 01:28:40PM -0500, joshua stein wrote:
> On the 2015 MacBook Pro and the 12" MacBook, the firmware reports a
> framebuffer size of 2880x1800 but the screens are 2560x1600 and
> 2304x1440. Our console ends up drawing text off screen and the
> latest few lines can't be read
I noticed a discrepancy in the instructions to enable rad(8). If you
were already using em1 for rtadvd(8) then rad(8) should also use em1 and
not em0. Also add two commas for better grammar.
Bryan
Index: faq/current.html
===
RCS fil
On Sun, Jul 22, 2018 at 11:50:07AM -0600, Theo de Raadt wrote:
> Better.
>
> It is important to not fall into the trap of doing marketing for
> vendors. But also keep in mind another product is likely months away,
> and then what to you do?
True. Good point. I also did not think about what kette
On Sun, Jul 22, 2018 at 07:36:32PM +0200, Mark Kettenis wrote:
> And it seems that at least the 500G an 1TB models have been marketed
> as SanDisk Extreme PRO:
>
>
> https://www.anandtech.com/show/12543/the-western-digital-wd-black-3d-nand-ssd-review
>
> The names are a bit long. Googling for
On Sun, Jul 22, 2018 at 11:19:00AM -0600, Theo de Raadt wrote:
> This is unreasonable.
>
> 1. Can I add High-performance to every 2nd line in this file? After all,
>I bet everyone would love to claim that for their hardware.
I'm sure. That's the only way the generation one and two hardware a
Here is the output from dmesg before and after.
nvme0 at pci3 dev 0 function 0 unknown vendor 0x15b7 product 0x5002 rev 0x00:
msi, NVMe 1.3
nvme0: WDS500G2X0C-00L350, firmware 101110WD, serial 181123456789
nvme0 at pci3 dev 0 function 0 "SanDisk WD Black High-performance NVMe SSD" rev
0x00: msi
On Fri, Jul 20, 2018 at 11:09:09AM +0200, Mark Kettenis wrote:
> Right. It's best if the names are unique and using
> pre-merger/takeover company names typically helps with that.
If that is the consensus then here is a diff. The WD Black
High-performance NVMe SSDs were never marketed under SanDis
On Thu, Jul 19, 2018 at 08:32:45PM +0200, Mike Belopuhov wrote:
> But at this point the origin of new devices is WD. I think since it's
> a new addition it should go by WD to reduce potential confusion in the
> future.
I would tend to agree. It would look rather strange to have a Sandisk WD
Black
I am wanting to add the WD Black High-performance NVMe SSD PCI
IDs to pcidevs and I am not sure how to proceed. WD bought Sandisk a
while back but the vendor ID is 15b7 which is Sandisk Corp. The product
itself is WD Black High-performance NVMe SSD and is labeled as Western
Digital. The vendor ID o
On Wed, Mar 14, 2018 at 10:27:10AM +1000, David Gwynne wrote:
> this makes netstart run "hostname foo0 up" for every interface that
> is configured. however, if you do not want an interface to be brought
> up on boot (you may just want to configure it) you can disable this
> by putting "down" in th
Ping. Any thoughts?
On Sun, Jan 28, 2018 at 05:26:12PM -0800, Bryan Vyhmeister wrote:
> I noticed that the order of listed Intel integrated graphics support is
> not consistent from newest to oldest as it is for Radeon devices on the
> same page. The patch puts Kaby Lake above Skylake
I noticed that the order of listed Intel integrated graphics support is
not consistent from newest to oldest as it is for Radeon devices on the
same page. The patch puts Kaby Lake above Skylake as it is 7th and then
6th generation respectively.
Bryan
Index: amd64.html
===
I was reading pkg_sign.1 and noticed that the description for the -o
option seems incorrect. The current pkg_sign.1 text says under the -o
option that "Otherwise, unsigned packages are created in the current
directory" where I think it should say "Otherwise, signed packages are
created in the curre
On Mon, Jul 24, 2017 at 10:20:22PM +0200, Mark Kettenis wrote:
> > Date: Mon, 24 Jul 2017 12:55:25 -0700
> > From: Bryan Vyhmeister
> >
> > On Mon, Jul 24, 2017 at 09:42:41PM +0200, Mark Kettenis wrote:
> > > > From: Bryan Vyhmeister
> > > >
&
I saw the following message a few times over the last few snapshots when
I do a reboot and noticed that 'shudown' should be 'shutdown'.
Bryan
Index: sys/dev/ic/nvme.c
===
RCS file: /cvs/src/sys/dev/ic/nvme.c,v
retrieving revision 1.
On Fri, Mar 17, 2017 at 05:28:59PM +0100, Ingo Schwarze wrote:
> Hi Bryan,
>
> since nobody else answered, and even though i don't know that
> much about hardware support: I don't think your patch should be
> committed.
>
> https://www.openbsd.org/socppc.html
>
> says:
> The OpenBSD/socppc po
I am not sure what happened to the patch tj@ committed but it is not
there for 61.html. Perhaps it was clobbered by another commit or was
this not left in because socppc was essentially retired after 5.8 since
there was no 5.9 or 6.0 release?
For reference:
http://marc.info/?l=openbsd-cvs&m=14889
On Mon, Dec 12, 2016 at 02:50:50PM +0100, Gerhard Roth wrote:
> The current umb(4) implementation needs one USB transfer for every packet
> that is sent. With the following patch, we can now aggregate several
> packets from the ifq into one single USB transfer.
>
> This may speed up the tx path. A
On Sat, Dec 10, 2016 at 10:47:31PM +, Stuart Henderson wrote:
> In case anyone is interested, here's a version of this diff against
> -current. It helps a lot for me. I'm not watching HD video while doing
> "make -j4", just things like trying to move the pointer around the screen
> and type int
On Wed, Dec 07, 2016 at 10:46:44AM +0100, Reyk Floeter wrote:
>
> > Am 05.12.2016 um 23:05 schrieb Bryan Vyhmeister :
> >
> > In responding to a post on misc@, I noticed that bioctl(8) uses all sd(4)
> > devices in the examples sections while softraid(4) uses wd(4)
On Wed, Dec 07, 2016 at 06:49:06AM +, Jason McIntyre wrote:
> On Mon, Dec 05, 2016 at 02:05:02PM -0800, Bryan Vyhmeister wrote:
> > In responding to a post on misc@, I noticed that bioctl(8) uses all sd(4)
> > devices in the examples sections while softraid(4) uses wd(4) devi
On Tue, Dec 06, 2016 at 08:01:12PM +0100, Adam Wolk wrote:
> On a side note it would be nice to have a OpenBSD-release shorthand on
> man.openbsd.org pointing to the latest release. That would help avoid
> a similar diff churn after 6.1 gets released.
Although I recognize my opinion does not carry
In responding to a post on misc@, I noticed that bioctl(8) uses all sd(4)
devices in the examples sections while softraid(4) uses wd(4) devices
for the chunks. This patch updates softraid.4 to use sd(4) devices as
well. I have not used a wd(4) device in years and I think it more
confusing to use ex
On Mon, Dec 05, 2016 at 09:38:04PM +, Stuart Henderson wrote:
> On 2016/11/26 14:57, Okan Demirmen wrote:
> >
> > In addition, I've changed the 'bind' and 'mousebind' config options to
> > 'bind-key' and 'bind-mouse', respectively. The 'unmap' option is replaced by
> > 'unbind-key' and 'unbind
On Thu, Nov 24, 2016 at 06:56:42PM +, Jason McIntyre wrote:
> ah. i have a habit of committing diffs from developers because i keep
> losing track of who has commit. this time i'm giving oks to people
> without commit...
>
> fixed, thanks for the mail, and sorry about the (perpetual) confusion
On Wed, Nov 23, 2016 at 04:20:25PM -0800, Bryan Vyhmeister wrote:
> I forgot about adding the newly supported Sierra Wireless EM7455 to the
> umb(4) man page.
>
> Bryan
>
>
> Index: share/man/man4/umb.4
>
I forgot about adding the newly supported Sierra Wireless EM7455 to the
umb(4) man page.
Bryan
Index: share/man/man4/umb.4
===
RCS file: /cvs/src/share/man/man4/umb.4,v
retrieving revision 1.5
diff -u -p -r1.5 umb.4
--- share/man/ma
This patch adds the Sierra Wireless EM7455 umb(4) device to usbdevs in
preparation for another patch to if_umb.c which adds full support for
the EM7455.
Bryan
Index: sys/dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
r
This patch accomplishes two things for umb(4) connections. One, some SIM
cards have a plus at the beginning of the phone number while others do
not. In my case, an AT&T Wireless SIM card in the US has the plus where
a T-Mobile SIM card in Germany does not. The output of ifconfig(8)
originally added
On Wed, Nov 09, 2016 at 12:10:53PM +1100, Jonathan Gray wrote:
> On Tue, Nov 08, 2016 at 05:03:32PM -0800, Bryan Vyhmeister wrote:
> > I noticed a typo in sys/dev/pv/vmt.c.
> >
> > Bryan
>
> There is a typo in your patch.
I suppose if you want to go with British Engl
I noticed a typo in sys/dev/pv/vmt.c.
Bryan
Index: sys/dev/pv/vmt.c
===
RCS file: /cvs/src/sys/dev/pv/vmt.c,v
retrieving revision 1.10
diff -u -p -r1.10 vmt.c
--- sys/dev/pv/vmt.c4 Oct 2016 09:59:44 - 1.10
+++ sys/dev/
On Mon, Sep 19, 2016 at 06:24:54PM -0700, Bryan Vyhmeister wrote:
> On Tue, Sep 20, 2016 at 02:11:41AM +0100, Stuart Henderson wrote:
> > Still seems a bit awkward, how about this?
> >
> > The
> > .Nm
> > device and the controller communicate using the
> >
On Tue, Sep 20, 2016 at 02:11:41AM +0100, Stuart Henderson wrote:
> Still seems a bit awkward, how about this?
>
> The
> .Nm
> device and the controller communicate using the
> OpenFlow 1.3 protocol.
Even better. I am very happy with that.
Bryan
This is a patch to reorder an awkward sentence in the switch(4) man
page. This may not be desired but it looks less awkward to me.
Bryan
Index: switch.4
===
RCS file: /cvs/src/share/man/man4/switch.4,v
retrieving revision 1.3
diff -
On Mon, Jun 20, 2016 at 12:34:17PM +0200, Stefan Sperling wrote:
> I found that my 8260 iwm(4) device has trouble associating to my 5 GHz
> AP, which runs OpenBSD with athn(4) in hostap mode. Most of the time
> it won't even get a DHCP lease. Some frames it believes it has sent
> are not even visib
On Wed, Jun 15, 2016, at 09:34 AM, Bryan Steele wrote:
> On Wed, Jun 15, 2016 at 12:32:00PM -0400, Bryan Steele wrote:
> > On Wed, Jun 15, 2016 at 11:23:53AM -0500, joshua stein wrote:
> > > Any ideas for a new name?
> >
> > NetBSD calls their equivalent driver genfb(4).
>
> I wonder if it could be
On Tue, Jun 14, 2016 at 11:56:14PM +0100, Stuart Henderson wrote:
> As far as I can make out, the FCC auth is to enable the radio rather
> than anything else, the command has to be sent over (qmi-over-)MBIM.
> I haven't had time to get a linux install to see how it behaves there
> but I would assum
On Tue, Jun 14, 2016 at 11:17:56PM +0200, Gerhard Roth wrote:
> Well, the device still refuses to turn on the radio and without it,
> there's no chance to register with the provider.
>
> That you see more information now is just due to the fact, that the
> state machine now continues beyond the "t
On Fri, Jun 10, 2016 at 09:43:36AM +0200, Gerhard Roth wrote:
> Hmm, I don't see the missing break. It is still stuck in the same
> state trying to turn on the radio and always getting non-confirmative
> resonses.
>
> If the break before "case UMB_S_RADIO:" is missing, I would expect
> to see a de
On Thu, Jun 09, 2016 at 10:31:58PM +0200, Gerhard Roth wrote:
> If that doesn't help, please set UMB_DEBUG and set umb_debug to 5.
I left that break commented out which perhaps I shouldn't have but below
is the output when I set an apn and bring umb0 up.
OpenBSD 6.0-beta (GENERIC.MP) #0: Thu Jun
On Thu, Jun 09, 2016 at 09:58:10PM +0100, Stuart Henderson wrote:
> You're getting further than me.
>
> Though, looking at list posts, it does seem that Lenovo is another
> vendor which requires the command being referred to as "fcc auth"
> in order to connect, at least in some of their cards.
Th
On Thu, Jun 09, 2016 at 10:31:58PM +0200, Gerhard Roth wrote:
> If you're using the latest version of the driver, the 'ifconfig ubm0 inet
> ...' isn't required anymore.
>
> But you probably have to set the default route after the interface is
> up.
Good to know. Thanks!
> Hmm, around here apart
On Wed, Jun 08, 2016 at 03:08:52PM +0200, Gerhard Roth wrote:
> I would be glad to hear from some people trying this with a real MBIM
> device.
I have a Sierra Wireless EM7455 MBIM device that I purchased with my
ThinkPad X260. I am very excited for this driver to make it into
OpenBSD. I am a litt
On Tue, May 31, 2016 at 06:43:16PM +0200, Martin Pieuchot wrote:
> I finally got my hands on a DELL Optiplex 3020. The BIOS on this
> machines uses the xHCI controller to handle the keyboard and mouse.
>
> Turns out that I badly copy/pasted the ehci(4) code to take over the
> HC from the BIOS. W
On Fri, May 20, 2016 at 10:46:27AM +0200, Theo Buehler wrote:
> > MicroTik to MikroTik typo correction.
>
> Thanks, committed, but without this:
>
> > -N1200 and the http://www.microtik.com";>MicroTik
> > +N1200 and the http://www.mikrotik.com";>MickoTik
Sorry about that. Thanks for catching tha
MicroTik to MikroTik typo correction.
Bryan
Index: www/socppc.html
===
RCS file: /cvs/www/socppc.html,v
retrieving revision 1.34
diff -u -p -r1.34 socppc.html
--- www/socppc.html 29 Mar 2016 14:58:59 - 1.34
+++ www/socp
The iop(4) driver has been gone for two years and tpms(4) has been
renamed to utpms(4) as well.
Bryan
Index: www/macppc.html
===
RCS file: /cvs/www/macppc.html,v
retrieving revision 1.250
diff -u -p -r1.250 macppc.html
--- www/macpp
I was just looking at macppc.html and noticed that lmc(4) was listed
along with art(4) as available WAN adapters and both were sent to the
bit bucket in the sky 13 months and 19 months ago respectively. I
checked the other platform pages and found lmc(4) also listed on
sparc64.html. Since we don't
This patch updates the boot command from 5.6 to 5.9.
Bryan
Index: macppc.html
===
RCS file: /cvs/www/macppc.html,v
retrieving revision 1.248
diff -u -p -r1.248 macppc.html
--- macppc.html 8 Apr 2016 01:58:04 - 1.248
+++ ma
On Tue, Apr 26, 2016 at 09:55:38AM +1000, Jonathan Gray wrote:
> We normally only add usb devices to usbdevs if they are used in drivers
> and sometimes if the device doesn't provide a string of it's own.
>
> I'd be surprised if a string is not supplied by the device in this case.
You're right. I
On Sun, Apr 24, 2016 at 05:01:41PM +1000, Jonathan Gray wrote:
> Device id appears on the latest generation of thinkpads.
> It looks like it should be compatible with the others?
>
> This requires the pcidevs changes I just committed.
>
> Index: sys/dev/pci/rtsx_pci.c
> ==
This patch adds device identification to src/sys/dev/usb/usbdevs for the
Sierra Wireless EM7455 as sold in the Lenovo ThinkPad X260. There is no
driver for the device (see thread on misc@) but it will show up
correctly in usbdevs(8) output.
Bryan
Index: sys/dev/usb/usbdevs
==
On Tue, Dec 22, 2015 at 08:30:15AM +0100, Theo Buehler wrote:
> Responsiveness of keyboard.backlight adjustment is now immediate
> rather than delayed by about one second.
I didn't test keyboard.backlight adjustment responsiveness initially on
the MacBookAir7,2 but, as you said as well, it is inst
On Mon, Dec 21, 2015 at 10:38:24PM +0100, Mark Kettenis wrote:
> However, since Apple's SMC implementation almost certainly changed
> over the years, it would be good to test this diff on a wider range of
> Apple hardware. Please check that all sensors are still present and
> are properly updated
On Wed, Dec 02, 2015 at 09:30:30AM -0700, Theo de Raadt wrote:
> I agree with Stuart.
>
> When these lists include chip numbers, that is valuable. Lists
> containing names like Belkin RandomProduct may be less helpful, but
> the case hasn't been proven the lists should be removed.
I completely a
On Sun, Nov 29, 2015 at 06:37:45PM +0100, Mark Kettenis wrote:
> Just in case I accidentally unplug he Thiunderbolt gadget... The
> bge_stop() function gains a "softonly" argumentlike we introduced in
> other network drivers.
This along with the ppb.c patch allows the Apple Thunderbolt Ethernet
a
On Sat, Nov 28, 2015 at 11:01:55PM -0700, Theo de Raadt wrote:
> > On Sat, Nov 28, 2015 at 10:44:48PM -0700, Theo de Raadt wrote:
> > > Mark has told me he thinks this chip model is likely to come up clean,
> > > so let's see what he gets working!
> >
> > Thanks for the background on that! In that
On Sat, Nov 28, 2015 at 10:44:48PM -0700, Theo de Raadt wrote:
> Mark has told me he thinks this chip model is likely to come up clean,
> so let's see what he gets working!
Thanks for the background on that! In that case, the ppb.c diff seems to
work perfectly. If it's useful, I have several Thund
I am resending this patch to the list. This patch adds the appropriate
identification to src/sys/dev/pci/pcidevs for the Broadcom BCM15700A2
chip which is the camera on recent MacBook Air (probably other Apple
systems as well) and also the Broadcom BCM4360 802.11ac wireless chip
found in recent App
On Sun, Nov 22, 2015 at 01:27:49PM -0800, Bryan Vyhmeister wrote:
> I noticed a patch come through a few minutes ago to add some pcidevs for
> other Apple systems so I added identifications for the BCM15700A2 chip
> which appears at least in the 2013/2014/2015 MacBook Air system. It
>
I somehow missed this thread before posting to misc@. I’m using the Nov
1 snapshot with an OpenBSD-only EFI install on the internal SSD of a
2013 MacBook Air and inteldrm(4) does attach but immediately after the
display is corrupted. I can start X just fine but the corruption
remains. I can quit fv
Apologies. Wrong list.
Bryan
I just noticed that the link and label don't match.
Bryan
--- www/openssh/specs.html 3 Oct 2013 15:35:45 - 1.5
+++ www/openssh/specs.html 7 Oct 2013 21:31:28 -
@@ -111,7 +111,7 @@ Source: http://datatracker.ietf
SHA-256 SSHFP Resource Records (new in OpenSSH 6.1).
Sorry about that. Attached instead of inline. My dmesg and Xorg.0.log
are now inline.
Bryan
OpenBSD 4.9-current (GENERIC.MP) #0: Sun Jun 19 17:02:51 PDT 2011
r...@nine.dsvc.net:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.6
Attached is my dmesg output and Xorg.0.log from my Dell Vostro A90. My
primary motivation for testing this was to see if I could disable
tapping and by default, that is how it works. I am now also able to
scroll with the touchpad. All of this works seamlessly without an
xorg.conf. Everything has be
80 matches
Mail list logo
