search for: fbs

...fer property? We don't have properties on the framebuffer. I guess you /could/ just add it internally to struct drm_framebuffer, and not bother exposing to userspace. I guess that would be a lot simpler, but it also means that atomic userspace can't use hotspots before we add properties to fbs. And doing that is a bit tricky since drm_framebuffer objects are meant to be invariant - this assumption is deeply in-grained into the code all over the place, everything just compares pointers when semantically it means to compare the entire fb (including backing storage pointer/offsets and every...

...fer property? We don't have properties on the framebuffer. I guess you /could/ just add it internally to struct drm_framebuffer, and not bother exposing to userspace. I guess that would be a lot simpler, but it also means that atomic userspace can't use hotspots before we add properties to fbs. And doing that is a bit tricky since drm_framebuffer objects are meant to be invariant - this assumption is deeply in-grained into the code all over the place, everything just compares pointers when semantically it means to compare the entire fb (including backing storage pointer/offsets and every...

.................................................... ............ Dr Tom C Cameron Genetics, Ecology and Evolution IICB, University of Leeds Leeds, UK Office: +44 (0)113 343 2837 Lab: +44 (0)113 343 2854 Fax: +44 (0)113 343 2835 Email: t.c.cameron@leeds.ac.uk Webpage: click here <http://www.fbs.leeds.ac.uk/staff/profile.php?tag=Cameron_TC> [[alternative HTML version deleted]]

I cant make the nouveau work with an arcade monitor, problably because the EDID. I can make modeline work fine to reduce the horizontal to 15khz, tested in a normal pc monitor (with ugly visual because the 15khz in horizontal). But when i try in the arcade monitor, dont show any image after xorg start. In official nvidia driver has an option NOEDID to force the driver to ignore information from

...will contribute to the development of improved methods and processes with a focus on imputation methods for missing data, compilation of regional and world aggregates, data analysis and validation methods. By way of example, with respect to methodological and technical work on Food Balance Sheet (FBS), the consultant would undertake the following duties: - Develop optimum imputation, analysis and/or validation methods for improved Supply Utilization Accounts (SUA's) and FBS; - Test and implement optimum statistical methods; - Provide high-level rec...

...Sorry, I failed to reference the original email. Here it is: <snip> I am a recent addition to Google's ChromeOS gfx team. I am currently working on display testing and reporting. An important part of this is our screen capture tool, which works by querying drm for crtcs, planes, and fbs. Unfortunately, there is only limited information available via drmModeGetFB(), which often wrong information when drmModeAddFB2() was used to create the fbs. For example, if the pixel format is NV12 or YUV420, the fb returned knows nothing about the additional buffer planes required by these fo...

...ramebuffer init sequence drm: revamp locking around fb creation/destruction drm: create drm_framebuffer_lookup drm/gma500: move fbcon restore to lastclose drm: revamp framebuffer cleanup interfaces drm: reference framebuffers which are on the idr drm: nest modeset locks within fpriv->fbs_lock drm/i915: fixup overlay stolen memory leak drm: push modeset_lock_all into ->fb_create driver callbacks drm: don't take modeset locks in getfb ioctl drm: fb refcounting for dirtyfb_ioctl drm: refcounting for sprite framebuffers drm: encapsulate crtc->set_config calls dr...

Fixes assertions when trying to attach textures to fbs with formats not supported by the render engines. See https://bugs.freedesktop.org/show_bug.cgi?id=73459 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Francisco, thanks for the review. Is this more like what you had in mind? Interesting that nv10/nv20 support different-bitness c...

Fixes assertions when trying to attach textures to fbs with formats not supported by the render engines. See https://bugs.freedesktop.org/show_bug.cgi?id=73459 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- In a perfect world I'd have separate callbacks for depth and color, but given the list of supported values, I don't thin...

...;> > >>> +static bool is_hdmi2_sink(struct drm_connector *connector) > >> You're usually known for adding const all around, why not const pointer > >> here and in all the other drm_* functions that call this? > > My current approach is to constify states/fbs/etc. but not so much > > crtcs/connectors/etc. Too much const can sometimes get in the way > > of things requiring that you remove the const later. But I guess > > in this case the const shouldn't really get in the way of anything > > because these are pretty much suppos...

................................................. ............ Dr Tom C Cameron Genetics, Ecology and Evolution IICB, University of Leeds Leeds, UK Office: +44 (0)113 343 2837 Lab: +44 (0)113 343 2854 Fax: +44 (0)113 343 2835 Email: t.c.cameron at leeds.ac.uk Webpage: click here <http://www.fbs.leeds.ac.uk/staff/profile.php?tag=Cameron_TC> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: test.txt Url: https://stat.ethz.ch/pipermail/r-help/attachments/20070220/82646d15/attachment.txt

...n->apertures; if (!hwa || !gena) return false; @@ -1501,6 +1500,28 @@ static bool fb_do_apertures_overlap(struct fb_info *gen, struct fb_info *hw) return false; } +void remove_conflicting_framebuffers(struct apertures_struct *a, const char *name) +{ + int i; + + /* check all firmware fbs and kick off if the base addr overlaps */ + for (i = 0 ; i < FB_MAX; i++) { + if (!registered_fb[i]) + continue; + + if (!(registered_fb[i]->flags & FBINFO_MISC_FIRMWARE)) + continue; + + if (fb_do_apertures_overlap(registered_fb[i]->apertures, a)) { + printk(KERN_ERR "fb...

...he original email. Here it is: > > <snip> > I am a recent addition to Google's ChromeOS gfx team. I am currently > working on display testing and reporting. An important part of this is > our screen capture tool, which works by querying drm for crtcs, planes, and > fbs. Unfortunately, there is only limited information available via > drmModeGetFB(), which often wrong information when drmModeAddFB2() was used > to create the fbs. For example, if the pixel format is NV12 or YUV420, > the fb returned knows nothing about the additional buffer planes requi...

...nline struct drm_fb_helper * > > >> >> I'm not sure if we should check for the dirty() callback at all. >> > > Hm, why do you think that? Drivers may already come with their own shadow buffer. Cirrus is an example of that. It uses shmem buffer objects as shadow fbs and internally updates the device frame buffer in its dirty callback. Using dirty() to select the shadow fbdev adds another buffer (and another memcpy) for no reason. Best regards Thomas > The thing with fbdev defio is that it only supports kmalloc and vmalloc > allocated memory (page->l...

...nline struct drm_fb_helper * > > >> >> I'm not sure if we should check for the dirty() callback at all. >> > > Hm, why do you think that? Drivers may already come with their own shadow buffer. Cirrus is an example of that. It uses shmem buffer objects as shadow fbs and internally updates the device frame buffer in its dirty callback. Using dirty() to select the shadow fbdev adds another buffer (and another memcpy) for no reason. Best regards Thomas > The thing with fbdev defio is that it only supports kmalloc and vmalloc > allocated memory (page->l...

...; +static bool is_hdmi2_sink(struct drm_connector *connector) > >>>> You're usually known for adding const all around, why not const pointer > >>>> here and in all the other drm_* functions that call this? > >>> My current approach is to constify states/fbs/etc. but not so much > >>> crtcs/connectors/etc. Too much const can sometimes get in the way > >>> of things requiring that you remove the const later. But I guess > >>> in this case the const shouldn't really get in the way of anything > >>> beca...

...lib/skl: Add gen9 specific igt_blitter_fast_copy() lib: Don't give a struct igt_buf * to fast_copy_pitch() lib: Split two helpers to build fast copy's dword0 and dword1 lib: Provide a raw version of the gen9 fast copy blits lib: Allow the creation of Ys/Yf tiled FBs testdisplay/skl: Add command line options for Yb/Yf tiled fbs lib/fb: Use PRIx64 for uint64_t in format string Daniel Vetter (27): tests/gem_exec_blt: Add subtest that uses dumb buffers tests/gem_concurrent_blt: Adjust subtest naming tests/gem_concurrent_blit: Fix ind...

...drm_set_preferred_mode); > > > > +static bool is_hdmi2_sink(struct drm_connector *connector) > > You're usually known for adding const all around, why not const pointer > here and in all the other drm_* functions that call this? My current approach is to constify states/fbs/etc. but not so much crtcs/connectors/etc. Too much const can sometimes get in the way of things requiring that you remove the const later. But I guess in this case the const shouldn't really get in the way of anything because these are pretty much supposed to be pure functions. > > &gt...

...a version 3.00 loaded. ahci 0000:09:00.0: version 3.0 ahci 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 ahci 0000:09:00.0: irq 757 (269) for MSI/MSI-X ahci 0000:09:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode ahci 0000:09:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs ahci 0000:09:00.0: setting latency timer to 64 ahci 0000:09:00.0: The port is not capable of FBS ahci 0000:09:00.0: The port is not capable of FBS scsi0 : ahci scsi1 : ahci ata1: SATA max UDMA/133 abar m2048@0xf7dff000 port 0xf7dff100 irq 757 ata2: SATA max UDMA/133 abar m2048@0xf...

...uot;lwh.num", "partogram", "age", "gestation", "cervix", "effaced", "membranes", "rd.interval", "action.line", "synto", "synto.time", "rom", "blood", "ctg", "fbs", "fbs.no", "iupc", "amnioinf", "ves", "anaesth", "delivery.mode", "perineum", "blood.loss", "transfus", "drugs", "retained.pl", "baby.no", "weight", "apgar1...