search for: planar

...ontinue allocating YUV buffers through >>>> CREATE_DUMB. >>> >>> I think, allocating YUV buffers through CREATE_DUMB interface is just >>> an *abuse* and *misuse* of this API for now. >>> >>> Take the NV12 format as an example, NV12 is YUV420 planar format, have >>> two planar: the Y-planar and the UV-planar. The Y-planar appear first >>> in memory as an array of unsigned char values. The Y-planar is followed >>> immediately by the UV-planar, which is also an array of unsigned char >>> values that contains p...

...gt;>>>> On the platforms I have been using (omap, tidss, xilinx, rcar) the >>>>> dumb >>>>> buffers are the only buffers you can get from the DRM driver. The >>>>> dumb >>>>> buffers have been used to allocate linear and multiplanar YUV buffers >>>>> for a very long time on those platforms. >>>>> >>>>> I tried to look around, but I did not find any mentions that >>>>> CREATE_DUMB >>>>> should only be used for RGB buffers. Is anyone outside the core &gt...

...uffers through >>>>> CREATE_DUMB. >>>> >>>> I think, allocating YUV buffers through CREATE_DUMB interface is just >>>> an *abuse* and *misuse* of this API for now. >>>> >>>> Take the NV12 format as an example, NV12 is YUV420 planar format, have >>>> two planar: the Y-planar and the UV-planar. The Y-planar appear first >>>> in memory as an array of unsigned char values. The Y-planar is >>>> followed >>>> immediately by the UV-planar, which is also an array of unsigned char >&...

...terisk/fax-out# tiffinfo FAX68.TIF TIFF Directory at offset 0x9160 Image Width: 1728 Image Length: 1173 Resolution: 204, 98 pixels/inch Bits/Sample: 1 Compression Scheme: CCITT Group 3 Photometric Interpretation: min-is-white FillOrder: lsb-to-msb Samples/Pixel: 1 Rows/Strip: 1173 Planar Configuration: single image plane Page Number: 0-3 Group 3 Options: EOL padding (4 = 0x4) TIFF Directory at offset 0x11eb6 Image Width: 1728 Image Length: 1173 Resolution: 204, 98 pixels/inch Bits/Sample: 1 Compression Scheme: CCITT Group 3 Photometric Interpretation: min-is-white F...

...>>> I have to disagree here. >>>> >>>> On the platforms I have been using (omap, tidss, xilinx, rcar) the dumb >>>> buffers are the only buffers you can get from the DRM driver. The dumb >>>> buffers have been used to allocate linear and multiplanar YUV buffers >>>> for a very long time on those platforms. >>>> >>>> I tried to look around, but I did not find any mentions that >>>> CREATE_DUMB >>>> should only be used for RGB buffers. Is anyone outside the core >>>> develo...

...t;>> CREATE_DUMB. > >>>> > >>>> I think, allocating YUV buffers through CREATE_DUMB interface is just > >>>> an *abuse* and *misuse* of this API for now. > >>>> > >>>> Take the NV12 format as an example, NV12 is YUV420 planar format, have > >>>> two planar: the Y-planar and the UV-planar. The Y-planar appear first > >>>> in memory as an array of unsigned char values. The Y-planar is followed > >>>> immediately by the UV-planar, which is also an array of unsigned char > &gt...

...PI's rules. >>> I have to disagree here. >>> >>> On the platforms I have been using (omap, tidss, xilinx, rcar) the dumb >>> buffers are the only buffers you can get from the DRM driver. The dumb >>> buffers have been used to allocate linear and multiplanar YUV buffers >>> for a very long time on those platforms. >>> >>> I tried to look around, but I did not find any mentions that CREATE_DUMB >>> should only be used for RGB buffers. Is anyone outside the core >>> developers even aware of it? >>> &g...

We need to replace several servers, quickly - four of our Dell PE 1950's died in one week. (!!!) So, we're looking around, and I was checking out IBM. I customized to what we want, and hit 'continue', and suddenly there's another $800 for a "system common planar" that's "required". Googling only finds specs with it - does anyone know what it is? I mean, it's not like it's the motherboard, right? mark

...) decoder) ========================================================================== [AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 320 x 240 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.33:1 - prescaling to correct movie aspect. VO: [xv] 320x240 => 320x240 Planar YV12 New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). subtitle font: load_sub_face failed. [...

...he UAPI's rules. > > > > I have to disagree here. > > > > On the platforms I have been using (omap, tidss, xilinx, rcar) the dumb > > buffers are the only buffers you can get from the DRM driver. The dumb > > buffers have been used to allocate linear and multiplanar YUV buffers > > for a very long time on those platforms. > > > > I tried to look around, but I did not find any mentions that CREATE_DUMB > > should only be used for RGB buffers. Is anyone outside the core > > developers even aware of it? > > > > If we don&...

...locations for diseased trees in 2004 and 2005 and want to know whether the patterns are independent. I would like to use both the 'gcross' and 'kcross' functions (in spatstat). I imported the data from two text files and created point objects using as.ppp. I then created a marked planar point pattern using ppp. I am fairly sure that everything worked, because when I ask for information about the data file, I get marked planar point pattern: 628 points multitype, with levels = w2004 w2005 window: rectangle = [ 607200 , 634800 ] x [ 3438400 , 3460400 ] (Note: the window values are...

...595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x32315659 (YV12) guid: 59563132-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x30323449 (I420) guid: 49343230-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1...

...phic coordinate system name: GCS_North_American_1927 Details Map Projection Name: Albers Conical Equal Area Standard Parallel: 29.500000 Standard Parallel: 45.500000 Longitude of Central Meridian: -96.000000 Latitude of Projection Origin: 23.000000 False Easting: 0.000000 False Northing: 0.000000 Planar Coordinate Information Planar Distance Units: meters Coordinate Encoding Method: coordinate pair Coordinate Representation Abscissa Resolution: 0.008192 Ordinate Resolution: 0.008192 Geodetic Model Horizontal Datum Name: North American Datum of 1927 Ellipsoid Name: Clarke 1866 Semi-major Axis: 63...

...ing the pixel format id, buffer plane information etc. </snip> ChromeOS has needed this functionality from the start, for both testing and error reporting. We got away with guessing the buffer's format (32bit xrgb) until now. We are now enabling overlays and more formats including multi-planar (e.g. NV12). Current getfb() reports neither the pixel format nor planar information. Without this information, going forward, our gfx testing is going to break. It would be great if we had access to higher level buffer structs (like gbm), but we generally don't since they would be created...

...fashion because there's no standard in encoding the *channel orderings*, what *channels are present*, and the *normalization*, and people don't agree on one thing for some reason. (perhaps being stubborn) My proposal is different because it solves all issues: it allows only Pantophonic (or planar/2D) signals if you wish, as probably most music and people will not even have a 3D system which includes height... at the same time you can specify a full 3D sphere encoding, or somewhere in between. The former is especially important because it needs far less number of channels and thus consumes f...

...ty of a spatial point process using 2 covariates from my data. After reading through the documentation, I have successfully created 2 "ppp" objects. The first ppp object is a list of coordinates where people exist and the second is where people do not exist as follows: > people_exist planar point pattern: 944 points window: rectangle = [73, 135] x [18, 54] units > people_empty planar point pattern: 2828 points window: rectangle = [73, 135] x [18, 54] units > Now, I also have observed values for two covariates, Z1 and Z2 for both the 944 and 2828 points in dataframe for...

...ding and for playing. eg. mplayer output: Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family [theora @ 0x892a230]Missing extradata! Could not open codec. VDecoder init failed :( Opening video decoder: [theora] Theora/VP3 VDec: vo config request - 640 x 480 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 2.37:1 - prescaling to correct movie aspect. VO: [xv] 640x480 => 1138x480 Planar YV12 Selected video codec: [theora] vfm: theora (Theora (free, reworked VP3)) =====================================================================...

.... so the error message is understandable for anyone. when this file is play with mplayer it shows as follow ========================================================================== Opening video decoder: [raw] RAW Uncompressed Video VDec: vo config request - 176 x 144 (preferred colorspace: Planar I420) VDec: using Planar I420 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 176x144 => 176x144 Planar I420 Selected video codec: [rawi420] vfm: raw (RAW I420) ========================================================================== but i want to know that...

On Tue, Nov 08, 2005 at 06:08:25PM +0800, illiminable wrote: > Why not just make it OggRawFOURCC, do we really need one stream format for > rgb, and one for yuv ? [snip] > I just meant oggRaw, not fourcc. Oh, thank god you corrected this. :-) I was contemplating an "OggVid" format, and here is why I'm steering against it (though, yes, this has been a topic of

On Tue, Nov 08, 2005 at 06:08:25PM +0800, illiminable wrote: > Why not just make it OggRawFOURCC, do we really need one stream format for > rgb, and one for yuv ? [snip] > I just meant oggRaw, not fourcc. Oh, thank god you corrected this. :-) I was contemplating an "OggVid" format, and here is why I'm steering against it (though, yes, this has been a topic of