Hi,
Yes, the USB device suspend/resume thing is a more generic
suspend/resume problem. Warner has some ideas - eg, registering a "is
this a new device?" method; the device driver will check if the device
has changed upon resume and optionally go through a detach/reattach
process. So for USB it cou
John,
I'm concerned that two issues may be getting conflated.
The issue I thought we were looking at was the failure of some systems
(T520, X220, T430) to resume after a number of PCI enhancements were MFCed.
This is completely unrelated to the USB issue I was experiencing when
trying to test the
Ok and I am sorry btw !
--
Jog
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Is my question clear, or would you like me to give further info (and which) ?
Thanks
--
Jog
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...
Do you really think this is appropriate ML? I think you should send your
question to freebsd-hackers.
Cheers,
Vit
--- Original message ---
From: deco33...@yandex.com
Date: 25 July 2015, 15:43:04
> Is my question clear, or would you like me to give further info (and which) ?
>
> Thanks
On Fri, 2015-07-24 at 16:17 -0400, Stari Karp wrote:
> > >>
> > >> > 1. VT module doesn't load.
> > >> > In /boot/loader.conf I have:
> > >> > kern.vty=vt
> > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I
> > >> > got just black screen and nothing more.
> > >>
I
On 04/16/2015 12:52 AM, Gareth Wyn Roberts wrote:
I've inserted code to print some values which show the differences between
specifying 4096 or 8192 for MSK_STAT_ALIGN. In both cases the status buffer
has length 0x4000 (8x2048=16K) but the alignments are different as expected,
respectively st
Hello,
I am learning the freebsd way to keep the time up to date.
We avoid to call hardware hardclock() every time we need a timestamp by
applying some math. I get the idea.
But, how do we know how far we are from the last hardclock()?
Are the updates to the "fake" timestamps occuring at a cons
On Sat, Jul 25, 2015 at 1:27 PM, Stari Karp wrote:
> On Fri, 2015-07-24 at 16:17 -0400, Stari Karp wrote:
>
>> > >>
>> > >> > 1. VT module doesn't load.
>> > >> > In /boot/loader.conf I have:
>> > >> > kern.vty=vt
>> > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I
