Displaying 5 results from an estimated 5 matches for "_correctly_".
Did you mean:
correctly_
2016 Jan 25
1
Intel Xorg driver for Intel HD graphics
> i915.preliminary_hw_support=1
Adding this to the boot - does not make it work on straight 7.2
I saw information about this - but it is mentioned on the page I
included that this was no longer needed with the files listed in the
link.
The kernel 4.4 installs and runs fine on the NUC5C. Its the
xorg-server package that is is my issue. Everything else ran fine.
The problem I'm trying
2023 Mar 13
1
[PATCH v2 0/2] [RFC] virtio-rng entropy leak reporting feature
...you chime in from the crypto/rng perspective if this
looks sane?
Jason has previously NACKed the patch without follow-up, and I don't
want the patch to linger without a path to merging, especially when
it's not clear what Jason meant.
> However, the new spec does allow us to do things _correctly_, i.e. not rely on asynchronous handling of events to re-seed the kernel. For example, we
> could achieve something like that by making use of the "copy-on-leak" operation, so that a flag changes value before vCPUs get resumed, so we know
> when a leak has happened when needed, e.g....
2016 Aug 17
5
code to sort otherwise-unsortable "ilist"s, e.g. symbol tables
Dear all,
The below has been tested quite thoroughly by now, including performance-testing by the way of
using a modified compiler that triggers the below while compiling at least an old part of LLVM
["Function.cpp"] and sorting a symbol table with >7000 global variables.
Unfortunately, the optimization I have been working on for which I _thought_ I needed the
ability to sort a
2008 Sep 08
13
list corner case
I'm curious how people think the following *should* be interpreted:
- one
2. two
http://babelmark.bobtfish.net/?markdown=-++one%0D%0A2.+two%0D%0A%0D%0A
As you can see, implementations split into three groups here:
(a) treat as an unordered list
Markdown.pl, Python markdown, MultiMarkdown, BlueCloth, MarkdownJ,
Showdown
(b) treat as an unordered list with an ordered
2015 Dec 19
2
For integer vectors, `as(x, "numeric")` has no effect.
As I tried to say on Dec. 11, there are two levels of "fix":
1. The fix to the complaint in the OP's subject heading is to conform to the default third argument, strict=TRUE: as(1L, "numeric") == 1.0
This generates some incompatibilities, as for classes that extend "numeric". But still leaves class(1.0) "numeric" and typeof(1.0) "double".