Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Lundberg, Johannes
I'm also newbie and I'm working on adding a sdhci_acpi driver for Intel's Atom SoC. I wonder if your device would work with the existing sdhci_pci driver. Maybe it just a matter of adding the device id and possibly setting some quirks or you might have to write a new driver for the host

new computer, strange usb messages at boot

2016-02-19 Thread Larry Rosenman
Does any of this look weird? What can I provide to help? Dell Inspiron 15 7559 Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered

Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Larry Rosenman
On 2016-02-19 22:25, Gary Corcoran wrote: On 2/19/2016 11:08 PM, Larry Rosenman wrote: On 2016-02-19 22:05, Mehmet Erol Sanliturk wrote: On Fri, Feb 19, 2016 at 7:58 PM, Larry Rosenman wrote: Great. Since I've never done that Any ideas of anyone that might be able to

Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Gary Corcoran
On 2/19/2016 11:08 PM, Larry Rosenman wrote: On 2016-02-19 22:05, Mehmet Erol Sanliturk wrote: On Fri, Feb 19, 2016 at 7:58 PM, Larry Rosenman wrote: Great. Since I've never done that Any ideas of anyone that might be able to help? Or where to even start?

Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Larry Rosenman
On 2016-02-19 22:05, Mehmet Erol Sanliturk wrote: On Fri, Feb 19, 2016 at 7:58 PM, Larry Rosenman wrote: Great. Since I've never done that Any ideas of anyone that might be able to help? Or where to even start? Perhaps https://www.nostarch.com/bsddrivers.htm

Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Mehmet Erol Sanliturk
On Fri, Feb 19, 2016 at 7:58 PM, Larry Rosenman wrote: > Great. Since I've never done that > > Any ideas of anyone that might be able to help? > > Or where to even start? > > > Perhaps https://www.nostarch.com/bsddrivers.htm FreeBSD Device Drivers ? Mehmet Erol

Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Larry Rosenman
Great. Since I've never done that Any ideas of anyone that might be able to help? Or where to even start? On Fri, Feb 19, 2016 at 08:48:02PM -0700, Warner Losh wrote: > You'll have to write a driver for it. > > Warner > On Feb 19, 2016 8:32 PM, "Larry Rosenman" wrote: >

Re: Realtek MMC/MMCSD reader?

2016-02-19 Thread Warner Losh
You'll have to write a driver for it. Warner On Feb 19, 2016 8:32 PM, "Larry Rosenman" wrote: > Any chance of supporting: > > none7@pci0:6:0:0: class=0xff card=0x522a10ec chip=0x522a10ec > rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor Co., Ltd.' > > >

Realtek MMC/MMCSD reader?

2016-02-19 Thread Larry Rosenman
Any chance of supporting: none7@pci0:6:0:0: class=0xff card=0x522a10ec chip=0x522a10ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' Thanks! ___ freebsd-current@freebsd.org mailing list

Re: Thinkpad T410: resume broken

2016-02-19 Thread John Baldwin
On Friday, February 19, 2016 06:38:27 PM Alexey Dokuchaev wrote: > On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote: > > On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote: > > > # pciconf -lc pci0:0:0 > > > hostb0@pci0:0:0:0: class=0x06 card=0x83191033

Re: Thinkpad T410: resume broken

2016-02-19 Thread Jean-Sébastien Pédron
On 18/02/2016 16:47, Alexey Dokuchaev wrote: > On a related note, how does one configure sc(4) with old drm (vs. > drm2) shall I need to try that? Hi! xf86-video-intel and xf86-video-ati do not handle modesetting for a long time now (almost three years), so they can't be used with the old "drm"

Re: Call for testing: Using ELF Tool Chain elfcopy as objcopy

2016-02-19 Thread Dmitry Marakasov
* Ed Maste (ema...@freebsd.org) wrote: JFYI, I've just updated my desktop to 295763 with WITH_ELFCOPY_AS_OBJCOPY=yes, and rebuilt all ~800 installed ports, no problems so far. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber:

Re: Thinkpad T410: resume broken

2016-02-19 Thread Alexey Dokuchaev
On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote: > > # pciconf -lc pci0:0:0 > > hostb0@pci0:0:0:0: class=0x06 card=0x83191033 chip=0x25908086 > > rev=0x04 hdr=0x00 > > cap 09[e0] = vendor (length 9)

Re: Thinkpad T410: resume broken

2016-02-19 Thread Alexey Dokuchaev
On Thu, Feb 18, 2016 at 10:02:17AM -0800, Adrian Chadd wrote: > [snip] > > Someone should sit me down with pizza and "help" me just modularise > the vesa/fb code so we can use it in vt. > > It isn't /that/ hard, I've just been preoccupied. And before it happens, someone(tm) could write a few

Re: Thinkpad T410: resume broken

2016-02-19 Thread Alexey Dokuchaev
On Thu, Feb 18, 2016 at 09:48:40AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote: > > On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote: > > > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > > > vesa.ko shouldn't be

Re: Memory modified after free in "MAP ENTRY" zone (vm_map_entry_t->read_ahead)

2016-02-19 Thread Andriy Gapon
On 18/02/2016 17:13, Konstantin Belousov wrote: > So this is arguably a fallout from r188331. > The following is somewhat non-insistent attempt to fix the problem. Kostik, thank you very much, I am testing the patch. > diff --git a/sys/vm/vm_fault.c b/sys/vm/vm_fault.c > index a7e3d37..cddf1eb