111–120 of 123 posts
Earlier quoted context omitted.
I think his point explains git beautifully.
True story. (I bet all of them had their terminal font set to Courier New Bold while doing so)
Is there something wrong with me?
Earlier quoted context omitted.
True story. (I bet all of them had their terminal font set to Courier New Bold while doing so)
I don't know if it's safe here to admit it, but I always kinda liked the xterm fonts. Is there something wrong with me?
Earlier quoted context omitted.
"After the end of the recovery interval the device must accept data transfers at any time." simply says that "hardware must be ready (in order to accept data transfer)"
But the "recovery interval" is not defined, leaving the device to decide what its "recovery interval" is and guaranteeing that software will not expect it to be less than 10ms.
USB System Software is expected to provide a “recovery” interval of 10 ms before the device attached to the port is expected to respond to data transfers
Earlier quoted context omitted.
That is a VERY general statement, most software engineers who do hardware stuff also know what takes to make it. You can't design a driver for a card without knowing everything about the card. And I'd say the same with hardware engineers. If you don't know how the software is going to run, how are you suppose to architect it. You can't make a piece of hardware without thinking about how the driver will work.
> You can't design a driver for a card without knowing everything about the card Strongly disagree with that statement, though I sincerely wish it were true. My company manufactures hardware and does not provide a reference driver for any OS. We provide binary blobs and textual "guidelines". For our hardware, driver authors operate without knowing any details beyond the interface.
Earlier quoted context omitted.
50ms should be quite enough i think. That's 5X the minimum, more than any proper device should ask for. If you want to be extreme you can make it 100ms but any more than that is way to extreme.
"50ms should be quite enough i think" If you are going to make a statement like that, make it "64ms ought to be enough for anyone". Either way, it won't help. If you write kernel code or interface with unknown hardware, you must be paranoid to the bone to get robust code. Double so if your kernel code talks with hardware you do not control. "more than any proper device should ask for." If devices asked for time, thin…
Earlier quoted context omitted.
Why on earth is all the text on that website set to font-weight:600 and using Courier New of all fonts? Incredibly hard to read.
I can read the website perfectly fine. It may not be shiny like all the iCrap, but it doesn't need to attract "average" users (e.g. spoiled, rich 12-year olds). I would rather prefer kernel hackers to do something useful, instead of wasting time and money to make every LKML archive look aesthetically beautiful. hackers != designers
Congrats! But how nobody analysed this bug for 8+ years is a bit of a mystery to me...
What are the conditions where this problem manifests? I have a Das Keyboard that sporadically become unresponsive until I unplug and plug it back in. How do I know if my problem is caused by the issue described in the article?
it happens after a resume from sleep?