search for: vics

On Wed, Jan 18, 2017 at 04:33:43PM +0000, Damien Lespiau wrote: > On Wed, Jan 18, 2017 at 11:27:16AM -0500, Ilia Mirkin wrote: > > Damien - did you ever test these mandatory modes on an actual > > commercial 3D TV or similar device? > > My main testing device was a Samsung TV with this 3D_present bit set and > all the advertised modes were working. Can't quite remember

I'm trying to figure out about factors, however the on-line documentation is rather sparse. I guess, factors are intended for grouping arrays members into categories, which R names "Levels". And so we have: * state <- c("tas", "sa", "qld", "nsw", "nsw", "nt", "wa", "wa",

On Wed, Jan 18, 2017 at 11:57 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Wed, Jan 18, 2017 at 11:41 AM, Damien Lespiau > <damien.lespiau at intel.com> wrote: >> On Wed, Jan 18, 2017 at 04:33:43PM +0000, Damien Lespiau wrote: >>> On Wed, Jan 18, 2017 at 11:27:16AM -0500, Ilia Mirkin wrote: >>> > Damien - did you ever test these mandatory modes

On Wed, Jan 18, 2017 at 11:41 AM, Damien Lespiau <damien.lespiau at intel.com> wrote: > On Wed, Jan 18, 2017 at 04:33:43PM +0000, Damien Lespiau wrote: >> On Wed, Jan 18, 2017 at 11:27:16AM -0500, Ilia Mirkin wrote: >> > Damien - did you ever test these mandatory modes on an actual >> > commercial 3D TV or similar device? >> >> My main testing device

On Wed, Jan 18, 2017 at 11:27:16AM -0500, Ilia Mirkin wrote: > Damien - did you ever test these mandatory modes on an actual > commercial 3D TV or similar device? My main testing device was a Samsung TV with this 3D_present bit set and all the advertised modes were working. Can't quite remember if that included the interleaved mode. -- Damien

I was getting a glicthy checkerboard mess at the cursor in some programs (konsol+) with # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=4107d1db-62a3-427c-8515-c954a103ce25 ro text quiet changed the command line in a blind attempt to: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=4107d1db-62a3-427c-8515-c954a103ce25 ro nouveau.config=NvForcePost=1

Hi, I'm attempting to add a "Julian Day" column to a data frame. Here is my code and the resulting data frame: vic.data <- read.table("C:/VIC/data/vic.data.csv", header=F) names(vic.data) <- c("year", "month", "day", "precip", "evap", "runoff", "baseflow", "Tsup",

Any guess's as to whats going on here? A new from source compile/install vic@zeus:/usr/local/bin$ wine wine: creating configuration directory '/home/vic/.wine'... Unknown option '-w' usage: wineserver [options] options: -d<n> set debug level to <n> -p make server persistent -h display this help message -s server will use shared memory

On 05/04/2017 04:00 AM, Pierre Moreau wrote: > Hello, > > Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards > in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the > Mesa-side, you will need >=17.0. Thanks - I suspected it was too new. I'm finding the monitor capabilities miss identified even if I use an older card - I'm

using an example from r online help > state <- c("tas", "sa", "qld", "nsw", "nsw", "nt", "wa", "wa", "qld", "vic", "nsw", "vic", "qld", "qld", "sa", "tas", "sa", "nt", "wa", "vic",

> > Dear Sir/Madam, > > I have a quick question, which I hope someone can help. > > I am using the levels function in R, which helps to summarize the number of > factors that I have in a vector in an ordered manner. > > Using an already existing example: > > > state <- c("tas", "sa", "qld", "nsw", "nsw",

...modes defined in 1.4. Only if you use features beyond 1.4 do we > > switch over to the HDMI 2.0 specific signalling. > > > The difference is in infoframes: > > HDMI 1.4 sets AVI infoframe VIC to 0, and sends HDMI_VIC in VSI. > > HDMI 2.0 sets AVI infoframe to non zero VICs introduced by > HDMI2.0/CEA-861-F, VSI can be omitted if I remember correctly, unless 3d > is in use. Like I said, The HDMI 1.4 method is used even with HDMI 2.0 sinks unless some feature gets used which can't be signalled via the HDMI 1.4 vendor specific infoframe. > > > So...

Hi Thierry et al. I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on Tegra124") graphics on Apalis TK1 is broken. During boot it fails loading the vic firmware: [ 1.595824] tegra-vic 54340000.vic: Direct firmware load for nvidia/tegra124/vic03_ucode.bin failed with error -2 [ 1.606140] tegra-vic: probe of 54340000.vic failed with error -2 Subsequently Tegra HDMI

...1.4 do we > >>> switch over to the HDMI 2.0 specific signalling. > >> > >> The difference is in infoframes: > >> > >> HDMI 1.4 sets AVI infoframe VIC to 0, and sends HDMI_VIC in VSI. > >> > >> HDMI 2.0 sets AVI infoframe to non zero VICs introduced by > >> HDMI2.0/CEA-861-F, VSI can be omitted if I remember correctly, unless 3d > >> is in use. > > Like I said, The HDMI 1.4 method is used even with HDMI 2.0 sinks unless > > some feature gets used which can't be signalled via the HDMI 1.4 vendor >...

On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > Hi Thierry et al. > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > Tegra124") graphics on Apalis TK1 is broken. During boot it fails > loading the vic firmware: > > [ 1.595824] tegra-vic 54340000.vic: Direct firmware load for > nvidia/tegra124/vic03_ucode.bin failed with

I've noticed that glm and lrm give extremely different results if you attempt to fit a saturated model to a dataset with zero cells. Consider, for instance the data from, Agresti's Death Penalty example [0]. The crosstab table is: , , PENALTY = NO VIC DEF BLACK WHITE BLACK 97 52 WHITE 9 132 , , PENALTY = YES VIC DEF BLACK WHITE BLACK 6 11

A little off-topic: I have the following hardware: 2610 XM NM-2V VIC-2BRI NT/TE IOS loaded: flash:c2600-ipvoice-mz.123-5d.bin" I get the following error while booting: %C542-1-UNKNOWN_VIC: VNM(1), vic daughter card has an unknown id of FF Is the VIC-2BRI compatible with the 2610XM? What IOS needs to be loaded? http://www.cisco.com/en/US/products/hw/modules/ps2641/products_tech_note0918

On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > Hi Thierry et al. > > > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > > Tegra124") graphics on Apalis TK1 is broken. During boot it fails > > loading the vic firmware: > > > > [

....4. Only if you use features beyond 1.4 do we >>> switch over to the HDMI 2.0 specific signalling. >> >> The difference is in infoframes: >> >> HDMI 1.4 sets AVI infoframe VIC to 0, and sends HDMI_VIC in VSI. >> >> HDMI 2.0 sets AVI infoframe to non zero VICs introduced by >> HDMI2.0/CEA-861-F, VSI can be omitted if I remember correctly, unless 3d >> is in use. > Like I said, The HDMI 1.4 method is used even with HDMI 2.0 sinks unless > some feature gets used which can't be signalled via the HDMI 1.4 vendor > specific infoframe....

On Mon, Dec 10, 2018 at 03:20:19PM +0000, Marcel Ziswiler wrote: > Hi Thierry > > On Mon, 2018-12-10 at 12:00 +0100, Thierry Reding wrote: > > On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > > > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > > > Hi Thierry et al. > > > > > > > > I noticed that