Damage including cosmetic damage , failure, loss or personal injury due to misuse, abuse, negligence, improper maintenance or storage, or to acts of nature or other causes beyond our control. Causes beyond our control include but are not limited to lightning strike, power surges, power outages and water damage. Image burn-in. Repair or replacement of warranted parts by other than an LGE authorized service centers. Units purchased or serviced outside of the U.
Product where the original factory serial numbers have been removed, defaced or changed in any way. Product sold and labeled as "as is, where is" or similar disclaimer. This corrects for that situation nicely. Turn on TV from standby mode:. Set the aspect ratio to "Just Scan":. If you look at the back of the LG owner's manual, it has a list of all the "supported" commands.
There are several others I've found that were not documented, but I'll save that for another writeup. If you pass the first parameter as "-s" followed by command and value, the script will first poll the current value from the TV and only set the new value if it is different.
If you are doing something periodically like adjusting the backlight, this can get rather annoying. The -s option helps avoid extra OSD distractions. Once you're talking to the TV, there are a number of interesting things you can do next. There were a few things that, despite going to a large display seemed novel and exciting, were a downgrade from my previous display.
For my purposes, I had two problems that I felt were very necessary to solve. Examples of using this: Turn on TV from standby mode:. To make the experience fit your profile, pick a username and tell us what interests you. We found and based on your interests.
Choose more interests. But, realistically, it's turning into a catch-all for my ridiculous ventures past and future in display-hacking, in general. The short of it is: I've an old PCI card that I wanted to add to my desktop, in addition to its built-in video, so I could run multiple monitors.
The longer of it is: This old PCI card is no longer supported by my OS, so I had to hack the driver, and recompile the kernel, and several other things to get it working. The longer-longer of it is: This old PCI card was designed for a special monitor.
I long ago took this PCI card apart to get that monitor working with standard VGA , and after months of hard work I'm using that special monitor on standard-VGA, while, more recently, after over a week of hard-work I'm using that special card to drive a standard VGA monitor dumb? That's in the "instructions", here. So I'm thinking about it Further ridiculosities: The Tuner in that board isn't particularly strong, last I tried it Maybe I should re-purpose that old 15in LCD, instead So, maybe Another use for my Single-To-Dual Converter!
Think about all the extra space! Third-monitor for my desktop? It's just collecting dust, now Thoughts To Ponder. Or there's that other 15incher The ol' Binary Clock Or a larger-screen for my logic-analyzer I wonder would dual-pixel be usefully-viewable for 4 channels? Maybe 5? And of course, there's MarioThing, which could stand to be a tiny bit larger to be more life-sized My digitizer and display go together, 12in.
But I don't have a DVI video card, as yet. Most displays I've encountered from STN through TFT use row drivers and column drivers which essentially are little more than shift-registers Three daisy-chained for the 24 columns Anodes and two separately daisy-chained for the 16 rows Cathodes, Invert those outputs.
Now you write a driver for this display, and basically you shift 1 active row onto the row-registers, and shift all the pixels in that row onto the column registers. Then shift the next row to be active, and shift in that row's pixels.
And so-forth. The row clock is your Hsync, the column clock is your pixel clock. Vsync is accomplished by resetting the row-registers to the first row reset the outputs to 0, then shift in one 1. Now, imagine you shift in more than 24 bits, say 25, on a row, what'd happen?
Well, as I recall of the ', it'd result in your image being shifted to the right, losing your first few columns off-screen So, most I've run into especially older ones. The first 64 data bits received are shifted to its 64 parallel outputs. Any bits received thereafter are shifted out of that chip and into the next. Once that second chip gets its 64 bits, it shifts any remaining bits to the next, and so-forth.
If you try to drive that with a x64 input signal, it will most-likely handle that just fine, as well. The first two happily receive and store and display the first pixels, then spit the remaining out for the third, which just happens to not be attached.
But they don't know that. Alright, so maybe that'd be difficult with today's displays, but maybe not. In fact many displays have test-points.
So, what-say your Raspberry Pi is wired to a x panel, and you configured it for x, and tapped off the daisy-chain with a bunch of 's? Maybe even 20 of them! Now you have up to outputs which can be toggled at Also, it shouldn't be too difficult to tap in a second display with a few trace-cuts and wires on the display itself The latter is something I'd been trying to figure out for some time, two displays on a lappy from the single display's input.
Or, heck, say you just want to add a friggin' indicator LED to your lappy's lid Or maybe you dug out a groovy old stencilled LCD from an old lappy with a HD activity indicator, battery indicator, etc.
Or even a VFD for such things Oh yeah, this came from my escapades with a TI over at Vintage Z80 palmtop compy hackery Here's Something for later avr-lvds-lcd why didn't I call that avr-fpdlink? And why do I continue to call it the former despite its now handling a slew of LCD interfaces? That's a nice screen, as I recall, and from my understanding of Mike's work running it with an AVR may actually be possible.
That setup displays HUGE blocks for each "pixel", 16x16 stretched onto a x display Thing is, the '85 has far too little RAM for something like this, so more than 64 colors isn't really doable as-is. On The Other Hand: I'd developed numerous image-ram-packing methods for various needs Above: 16x16 on a x display, refreshing at 2Hz with vertical dithering on red and green channels from full-on to full-off gives 4 shades, each.
Slow refresh captured partway down the image as the "question block" "shimmers" between different copper-ish hues, making it look like metal The image is drawn vertically, bottom to top, the white at the top is where the RAM was maxed-out from too many color-transitions. Each vertical pseudo-pixel is represented in memory as a color and number of pixels packed into each byte. Note how text uses a lot of color-changes, so uses far too much memory to rotate the display to landscape.
And the three rainbows of blue almost look the same due to gamma, I guess. That can't really be changed, due to the pseudo-lvds implementation limits TODO: This project-page could use some serious redoing See also VFD Panel-filter and avr-lvds-lcd binary-clock.
Sitting in the laundry room atop the donation-bin B Stand is extremely wobbly, touching the on-screen buttons has no effect without grabbing the display from behind for support. Should I replace my 33in TV? Gain some surface-space? Maybe even hang it on the wall? Crud, do I understand these newfangled resolution-standards correctly? Lessee, my 18incher is x, my SGI is x Maybe both Financially, I should probably sell the thing Man, how times've changed.
Whelp, some thinking to do, I guess But, no info about what shows are coming up in the future Pretty cool what can be done with this thing via the serial-port! I wrote down all my experiments Apparently, someone else came up with a pretty in-depth analysis and an awe-inspiring level of hackery , but not the info I'm currently looking for. There's lots of debug-data, and also a Mini-Shell It's taken a bit of experimenting with a bunch of the functions So I went through the list of functions, looking for others There're a couple really obvious looking ones such as 'PrintEit' and 'PrintEtt' Interestingly, it actually shows an disassembly-listing of where it crashed Here's a sample, 'cause I think it's cool anyhow:.
The last log got me thinking a bit more about my old display projects e. And, I remembered Some many? So, basically, what that means is:.
0コメント