Date: Fri, 26 Dec 2014 10:44:54 +0100 From: Bernd Walter <ticso@cicely7.cicely.de> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-arm@freebsd.org, ito <egunther@warwick.net> Subject: Re: RPI, config.txt: overscan, not working Message-ID: <20141226094454.GA53062@cicely7.cicely.de> In-Reply-To: <1419547193.1018.181.camel@freebsd.org> References: <1414774843.3499.18.camel@res-cmts> <1414917964.3427.2.camel@res-cmts> <1415062647.7543.9.camel@res-cmts> <1419547193.1018.181.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 25, 2014 at 03:39:53PM -0700, Ian Lepore wrote: > While searching for something else I just ran across this info: > > overscan_scale=1 caused the output of openFrameworks to respect > the overscan_left, overscan_right, top and bottom settings with > the use of an LCD display connected via composite. > > So maybe just adding that to config.txt would make your overscan > settings work right. I found that at: > > http://elinux.org/RPiconfig I have had a similar kind of problem long time ago. Story was a 1024x600 LC-display attached via converter to HDMI. Per default displayed 1024x768 with last 168 rows missing at bottom as HDMI specs only knows mode numbers with fixed resolutions. With LCD vendor supplied config.txt parameters I made it work under bootcode and Linux, but not under FreeBSD. I remember that Linux/bootcode behavour was very unexpected. I think it was something like this (don't remember exactly) in that top overscan removed one per pixel on top and bottom overscan removed 2 pixel on bottom, but also shifted the display up by one pixel. Under FreeBSD however the parameters behaved differently, so that the only option to remove bottom lines was to also remove top lines, which left 168 unused pixels on the top. IIRC I send a mail to this list about this problem. Never tested again since then. > On Mon, 2014-11-03 at 19:57 -0500, ito wrote: > > Hi, > > > > > > I Discovered that the framebuffer_width and framebuffer_height sizes > > seem to work but the overscan_left, overscan_right, etc. not as much. > > > > I have settled on > > > > framebuffer_width=720 > > framebuffer_height=400 > > > > referenced a well commented config.txt although solely added the two > > framebuffer entries to the existing config.txt because the overscan did > > not seem to work. > > > > https://raw.githubusercontent.com/Evilpaul/RPi-config/master/config.txt > > > > > > Thanks for any advice, > > > > ito > > > > On Sun, 2014-11-02 at 03:46 -0500, ito wrote: > > > Is there anyone with an idea as to how I can stop the text from spilling > > > off the screen. > > > > > > The display is in excess of 1/2 an inch all around. > > > > > > Thanks, > > > > > > ito > > > > > > > > > > > > On Fri, 2014-10-31 at 13:00 -0400, ito wrote: > > > > Hello, > > > > > > > > I have a raspberry pi, > > > > > > > > Model B Revision 2.0 (512MB) > > > > which has the logo along with: > > > > Raspberry Pi > > > > (c)2011.12 > > > > written on it. > > > > > > > > I have obtained a image for freebsd to run from here: > > > > > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/10.0/ > > > > > > > > > > > > I uncompressed the image on a OpenSUSE system, and used, > > > > > > > > sudo dd if=FreeBSD-10.0-RELEASE-arm-armv6-RPI-B-20140131-r260789.img > > > > of=/dev/sdd > > > > > > > > to put the image on a micro SD... with that card and adapter I have > > > > successfully boot freebsd. > > > > > > > > The problem I am facing now is that I am using the yellow SVGA (RCA type > > > > plug) cables to use an old Television as a monitor, with this setup I > > > > have an issue with the text running off of the screen. > > > > > > > > I have tried the config.txt file with > > > > overscan_disable=0 > > > > overscan_left=20 > > > > overscan_right=20 > > > > overscan_top=20 > > > > overscan_bottom=20 > > > > > > > > > > > > added to the existing config.txt > > > > > > > > > > > > > > > > I have tried to load vesa: > > > > > > > > kldload vesa > > > > > > > > where I get a prompt that it does not exist. > > > > > > > > I looked in the kernel directory (/boot/kernel/) and there is no vesa, > > > > not sure what that means. > > > > > > > > > > > > I am assuming that there is something that is not happening with the > > > > config.txt. I saw mention of using the files here to replace the files > > > > on the pi; > > > > > > > > https://github.com/raspberrypi/firmware > > > > > > > > > > > > SO, essentially, how do I get the text to stop from spilling off of the > > > > screen (command prompt-no gui). > > > > > > > > > > > > Thank You, > > > > > > > > ito > > > > > > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141226094454.GA53062>