> > I guess RPi provides a similar feature, and you need not manually handle > them using the config.txt file. >
The rPI BSP is a mess compared to the beaglebone. As far as I can tell there is nothing standard about it. However, it does make some things easier. Just as an example, here is some of the file structure, on my rPI3 Rasbian Jessie. william@rpi:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─sda1 8:1 0 931.5G 0 part mmcblk0 179:0 0 14.7G 0 disk ├─mmcblk0p1 179:1 0 60M 0 part /boot └─mmcblk0p2 179:2 0 14.6G 0 part / william@rpi:~$ ls /boot/ bcm2708-rpi-b.dtb bcm2710-rpi-3-b.dtb COPYING.linux fixup_x.dat LICENCE.broadcom start_db.elf bcm2708-rpi-b-plus.dtb bootcode.bin fixup_cd.dat issue.txt LICENSE.oracle start.elf bcm2708-rpi-cm.dtb cmdline.txt fixup.dat kernel7.img overlays start_x.elf bcm2709-rpi-2-b.dtb config.txt fixup_db.dat kernel.img start_cd.elf william@rpi:~$ cat /boot/cmdline.txt dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait william@rpi:~$ cat /boot/config.txt # For more options and information see # http://www.raspberrypi.org/documentation/configuration/config-txt.md # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan #disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable the lirc-rpi module #dtoverlay=lirc-rpi # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on On Sun, Jun 19, 2016 at 8:48 AM, TJF <[email protected]> wrote: > > > Am Sonntag, 19. Juni 2016 00:18:00 UTC+2 schrieb epi kao: >> >> thanks, and yes i already knew this link. >> But there is only explained how to read (for debug) the EDID infos. That >> is not really usefull. I need more functions as only resolution and refresh >> rate.... >> >> So it seems that with a raspberry i have more adjust functions to set the >> hdmi output-timings? >> > > Why do you think you have to provide this additional information? Let the > frame buffer driver compute them. Therefor, as William mentioned, specify > the cmdline variable in file /boot/uEnv.txt like > > >> cmdline=coherent_pool=1M quiet *video=HDMI-A-1:800x480M@60e* >> cape_universal=disable init=/lib/systemd/systemd >> > > Note the "M" after the resolution here. It requires individual calculation > of the timings (in contrast to reading them from a pre-defined table, see > framebuffer documentation for details). That way you can skip EDID and > specify any resolution in a convenient way. I guess RPi provides a similar > feature, and you need not manually handle them using the config.txt file. > > BR > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/a25953ef-3420-4ad2-92e7-285418c34488%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/a25953ef-3420-4ad2-92e7-285418c34488%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrBbZXQ0VPZvwX%2B7huDJCYHjDwr0SZbO5xdc%2BgoZvt1AA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
