Re: glxinfo: R200 VS FGLRX side by side...
Vladimir's glxtest code may be helpful in figuring out the missing bits if anyone is so inclined... Are you implying that this program will/could work with the fglrx driver? glxtest itself should work with *any* driver that does direct rendering. However, a suitable modification of instrumentation.c file may be required. What it does is capture contents of active memory maps (i.e. shared memory) during various points of execution of test program. In the case of Radeons, these shared memory maps contain streams of command packets and there is a handy script to print them in computer-English. best Vladimir Dergachev Alex __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
--- Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Fri, 1 Oct 2004 08:52:58 -0700 (PDT), Mike Mestnik
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > --- Alex Deucher <[EMAIL PROTECTED]> wrote:
> >
> > > On Thu, 30 Sep 2004 11:27:28 -0700, Ian Romanick <[EMAIL PROTECTED]>
> wrote:
> > > > Mike Mestnik wrote:
> > > >
> > > > > Here is a straigth diff, I didn't do a udiff since I think we
> all
> > > know the
> > > > > glxinfo output fairly well. I did make one change s/, $//g and
> s/,
> > > /\n
> > > > > /g. I'm also attaching the 'source'.
> > > >
> > > > A better way to get "meaningful" diffs is to pipe the output of
> > > glxinfo
> > > > to "grep GL_ | sed 's/, /\n/g' | sort -u". It's a bit more tricky
> for
> > > > GLX extensions because there are multiple listings for that
> (client,
> > > > server, and "combined").
> > > >
> > > > Looking at the list, I noticed a couple of odd things. Why don't
> the
> > > > ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
> > > > GL_{ARB,EXT}_blend_equation_separate? Beyond that, there are
> > > basically
> > > > 5 groups of useful extensions that they have but we don't:
> > > >
> > > > - GL_ARB_texture_env_crossbar
> > > > - GL_ARB_occlusion_query and similar extensions.
> > > > - GL_ARB_point_parameters (I thought support was added for this?)
> > > > - GL_EXT_multi_draw_arrays
> > > > - GL_EXT_fog_coord
> > > >
> > > > Crossbar, point parameters, and multi draw arrays should be easy
> > > enough
> > > > to add. I tried to add support for fog coord, but there's some
> bit of
> > > > documentation that we're missing. I just could not get it to work
> in
> > > > TCL mode. :( For occlusion query, we're missing a significant
> amount
> > > of
> > > > documentation.
> > > >
> > >
> > > Vladimir's glxtest code may be helpful in figuring out the missing
> > > bits if anyone is so inclined...
> > >
> > Are you implying that this program will/could work with the fglrx
> driver?
>
This wasn't ovious by the documentation, thought it dose answer my Q as to
why there is all the guess work involved in using glxtest.
> Well, yeah. that's how it works. It captures commands sent to the
> card which can then be decoded to figure out how things work. it
> should work with any card supported by fglrx.
>
LOL, it might but if GL_EXT_fog_coord dosen't work for the r200, even with
the fglrx driver, it's of little use.
I could be doing something wrong, like using an SDL example.
http://nehe.gamedev.net/data/lessons/linuxsdl/lesson41.tar.gz
> Alex
>
> >
> > > Alex
> > >
> >
> >
>
>
> ---
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give
> us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> --
> ___
> Dri-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>
___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
On Fri, 1 Oct 2004 08:52:58 -0700 (PDT), Mike Mestnik
<[EMAIL PROTECTED]> wrote:
>
>
>
> --- Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 30 Sep 2004 11:27:28 -0700, Ian Romanick <[EMAIL PROTECTED]> wrote:
> > > Mike Mestnik wrote:
> > >
> > > > Here is a straigth diff, I didn't do a udiff since I think we all
> > know the
> > > > glxinfo output fairly well. I did make one change s/, $//g and s/,
> > /\n
> > > > /g. I'm also attaching the 'source'.
> > >
> > > A better way to get "meaningful" diffs is to pipe the output of
> > glxinfo
> > > to "grep GL_ | sed 's/, /\n/g' | sort -u". It's a bit more tricky for
> > > GLX extensions because there are multiple listings for that (client,
> > > server, and "combined").
> > >
> > > Looking at the list, I noticed a couple of odd things. Why don't the
> > > ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
> > > GL_{ARB,EXT}_blend_equation_separate? Beyond that, there are
> > basically
> > > 5 groups of useful extensions that they have but we don't:
> > >
> > > - GL_ARB_texture_env_crossbar
> > > - GL_ARB_occlusion_query and similar extensions.
> > > - GL_ARB_point_parameters (I thought support was added for this?)
> > > - GL_EXT_multi_draw_arrays
> > > - GL_EXT_fog_coord
> > >
> > > Crossbar, point parameters, and multi draw arrays should be easy
> > enough
> > > to add. I tried to add support for fog coord, but there's some bit of
> > > documentation that we're missing. I just could not get it to work in
> > > TCL mode. :( For occlusion query, we're missing a significant amount
> > of
> > > documentation.
> > >
> >
> > Vladimir's glxtest code may be helpful in figuring out the missing
> > bits if anyone is so inclined...
> >
> Are you implying that this program will/could work with the fglrx driver?
Well, yeah. that's how it works. It captures commands sent to the
card which can then be decoded to figure out how things work. it
should work with any card supported by fglrx.
Alex
>
> > Alex
> >
>
>
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
--- Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Thu, 30 Sep 2004 11:27:28 -0700, Ian Romanick <[EMAIL PROTECTED]> wrote:
> > Mike Mestnik wrote:
> >
> > > Here is a straigth diff, I didn't do a udiff since I think we all
> know the
> > > glxinfo output fairly well. I did make one change s/, $//g and s/,
> /\n
> > > /g. I'm also attaching the 'source'.
> >
> > A better way to get "meaningful" diffs is to pipe the output of
> glxinfo
> > to "grep GL_ | sed 's/, /\n/g' | sort -u". It's a bit more tricky for
> > GLX extensions because there are multiple listings for that (client,
> > server, and "combined").
> >
> > Looking at the list, I noticed a couple of odd things. Why don't the
> > ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
> > GL_{ARB,EXT}_blend_equation_separate? Beyond that, there are
> basically
> > 5 groups of useful extensions that they have but we don't:
> >
> > - GL_ARB_texture_env_crossbar
> > - GL_ARB_occlusion_query and similar extensions.
> > - GL_ARB_point_parameters (I thought support was added for this?)
> > - GL_EXT_multi_draw_arrays
> > - GL_EXT_fog_coord
> >
> > Crossbar, point parameters, and multi draw arrays should be easy
> enough
> > to add. I tried to add support for fog coord, but there's some bit of
> > documentation that we're missing. I just could not get it to work in
> > TCL mode. :( For occlusion query, we're missing a significant amount
> of
> > documentation.
> >
>
> Vladimir's glxtest code may be helpful in figuring out the missing
> bits if anyone is so inclined...
>
Are you implying that this program will/could work with the fglrx driver?
> Alex
>
__
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
On Thu, 30 Sep 2004 21:21:43 +0200, Philipp Klaus Krause <[EMAIL PROTECTED]> wrote:
> Ian Romanick schrieb:
>
> >
> > Looking at the list, I noticed a couple of odd things. Why don't the
> > ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
> > GL_{ARB,EXT}_blend_equation_separate?
>
> ATI sometimes makes strage decicions about the features their drivers
> support: Even though the r200 could support GL_ARB_vertex_shader just
> as the r300 does, they only expose GL_ARB_vertex_program.
sure, to sell more new hardware... They also might have not felt it
was worth the time to re-architect the existing driver to add a new
feature to an old product, especially if it would have involved major
work.
Alex
>
> > Beyond that, there are basically
> > 5 groups of useful extensions that they have but we don't:
> >
> > - GL_ARB_texture_env_crossbar
> > - GL_ARB_occlusion_query and similar extensions.
> > - GL_ARB_point_parameters (I thought support was added for this?)
> > - GL_EXT_multi_draw_arrays
> > - GL_EXT_fog_coord
> >
>
> I once tried simply enabling GL_EXT_multi_draw_arrays, but there was
> a problem: When calling glMultiDrawElementsEXT while creating a display
> list the r200 driver called a Mesa function which wasn't to be called
> when creating display lists.
>
> Philipp
>
>
>
>
> ---
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> --
> ___
> Dri-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
On Thu, 30 Sep 2004 11:27:28 -0700, Ian Romanick <[EMAIL PROTECTED]> wrote:
> Mike Mestnik wrote:
>
> > Here is a straigth diff, I didn't do a udiff since I think we all know the
> > glxinfo output fairly well. I did make one change s/, $//g and s/, /\n
> > /g. I'm also attaching the 'source'.
>
> A better way to get "meaningful" diffs is to pipe the output of glxinfo
> to "grep GL_ | sed 's/, /\n/g' | sort -u". It's a bit more tricky for
> GLX extensions because there are multiple listings for that (client,
> server, and "combined").
>
> Looking at the list, I noticed a couple of odd things. Why don't the
> ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
> GL_{ARB,EXT}_blend_equation_separate? Beyond that, there are basically
> 5 groups of useful extensions that they have but we don't:
>
> - GL_ARB_texture_env_crossbar
> - GL_ARB_occlusion_query and similar extensions.
> - GL_ARB_point_parameters (I thought support was added for this?)
> - GL_EXT_multi_draw_arrays
> - GL_EXT_fog_coord
>
> Crossbar, point parameters, and multi draw arrays should be easy enough
> to add. I tried to add support for fog coord, but there's some bit of
> documentation that we're missing. I just could not get it to work in
> TCL mode. :( For occlusion query, we're missing a significant amount of
> documentation.
>
Vladimir's glxtest code may be helpful in figuring out the missing
bits if anyone is so inclined...
Alex
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
Ian Romanick schrieb:
Looking at the list, I noticed a couple of odd things. Why don't the
ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
GL_{ARB,EXT}_blend_equation_separate?
ATI sometimes makes strage decicions about the features their drivers
support: Even though the r200 could support GL_ARB_vertex_shader just
as the r300 does, they only expose GL_ARB_vertex_program.
Beyond that, there are basically
5 groups of useful extensions that they have but we don't:
- GL_ARB_texture_env_crossbar
- GL_ARB_occlusion_query and similar extensions.
- GL_ARB_point_parameters (I thought support was added for this?)
- GL_EXT_multi_draw_arrays
- GL_EXT_fog_coord
I once tried simply enabling GL_EXT_multi_draw_arrays, but there was
a problem: When calling glMultiDrawElementsEXT while creating a display
list the r200 driver called a Mesa function which wasn't to be called
when creating display lists.
Philipp
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
Mike Mestnik wrote:
Here is a straigth diff, I didn't do a udiff since I think we all know the
glxinfo output fairly well. I did make one change s/, $//g and s/, /\n
/g. I'm also attaching the 'source'.
A better way to get "meaningful" diffs is to pipe the output of glxinfo
to "grep GL_ | sed 's/, /\n/g' | sort -u". It's a bit more tricky for
GLX extensions because there are multiple listings for that (client,
server, and "combined").
Looking at the list, I noticed a couple of odd things. Why don't the
ATI drivers support GL_{ARB,EXT,NV}_texture_rectange or
GL_{ARB,EXT}_blend_equation_separate? Beyond that, there are basically
5 groups of useful extensions that they have but we don't:
- GL_ARB_texture_env_crossbar
- GL_ARB_occlusion_query and similar extensions.
- GL_ARB_point_parameters (I thought support was added for this?)
- GL_EXT_multi_draw_arrays
- GL_EXT_fog_coord
Crossbar, point parameters, and multi draw arrays should be easy enough
to add. I tried to add support for fog coord, but there's some bit of
documentation that we're missing. I just could not get it to work in
TCL mode. :( For occlusion query, we're missing a significant amount of
documentation.
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: glxinfo: R200 VS FGLRX side by side...
On Thu, 2004-09-30 at 05:52, Mike Mestnik wrote: > I'm interested in switching back and fourth, if any one has some info on > doing this better I'd like to know. Right now I'm symlinking > libGL-fglrx.so.1.2 or libGL-dri.so.1.2 into libGL.so.1.2. I also have to > unload and load kmods too, I do this by hand as well. I can go from DRI > to fglrx fine, but to go back I have to reboot first. Gentoo's opengl-update script works great for this, if you feel like moving a few files around on your system. You can grab the most recent version at http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/x11-base/opengl-update/files/opengl-update-1.8.1?rev=HEAD&content-type=text/plain -- Donnie Berkholz Gentoo Linux signature.asc Description: This is a digitally signed message part
glxinfo: R200 VS FGLRX side by side...
I'm interested in switching back and fourth, if any one has some info on doing this better I'd like to know. Right now I'm symlinking libGL-fglrx.so.1.2 or libGL-dri.so.1.2 into libGL.so.1.2. I also have to unload and load kmods too, I do this by hand as well. I can go from DRI to fglrx fine, but to go back I have to reboot first. Here is a straigth diff, I didn't do a udiff since I think we all know the glxinfo output fairly well. I did make one change s/, $//g and s/, /\n /g. I'm also attaching the 'source'. 6a7 > GLX_ARB_multisample 10,11c11,16 < client glx vendor string: ATI < client glx version string: 1.3 --- > GLX_OML_swap_method > GLX_SGI_make_current_read > GLX_SGIS_multisample > GLX_SGIX_fbconfig > client glx vendor string: SGI > client glx version string: 1.2 12a18,20 > GLX_ARB_get_proc_address > GLX_ARB_multisample > GLX_EXT_import_context 15c23,34 < GLX_EXT_import_context --- > GLX_MESA_allocate_memory > GLX_MESA_swap_control > GLX_MESA_swap_frame_usage > GLX_OML_swap_method > GLX_OML_sync_control > GLX_SGI_make_current_read > GLX_SGI_swap_control > GLX_SGI_video_sync > GLX_SGIS_multisample > GLX_SGIX_fbconfig > GLX_SGIX_visual_select_group > GLX extensions: 18,20c37 < GLX_ATI_pixel_format_float < GLX_ATI_render_texture < GLX extensions: --- > GLX_EXT_import_context 23,26c40,51 < GLX_EXT_import_context < OpenGL vendor string: ATI Technologies Inc. < OpenGL renderer string: RADEON 8500 DDR Generic < OpenGL version string: 1.3.4510 (X4.3.0-3.12.0) --- > GLX_MESA_allocate_memory > GLX_MESA_swap_control > GLX_MESA_swap_frame_usage > GLX_OML_swap_method > GLX_SGI_video_sync > GLX_SGIS_multisample > GLX_SGIX_fbconfig > GLX_SGIX_visual_select_group > OpenGL vendor string: Tungsten Graphics > Inc. > OpenGL renderer string: Mesa DRI R200 20040906 AGP 4x TCL > OpenGL version string: 1.3 Mesa 6.2 27a53,54 > GL_ARB_imaging > GL_ARB_multisample 29,33d55 < GL_EXT_texture_env_add < GL_EXT_compiled_vertex_array < GL_S3_s3tc < GL_ARB_occlusion_query < GL_ARB_point_parameters 39d60 < GL_ARB_texture_env_crossbar 41a63 > GL_ARB_texture_rectangle 43d64 < GL_ARB_vertex_blend 47,58d67 < GL_ATI_element_array < GL_ATI_envmap_bumpmap < GL_ATI_fragment_shader < GL_ATI_map_object_buffer < GL_ATI_texture_env_combine3 < GL_ATI_texture_mirror_once < GL_ATI_vertex_array_object < GL_ATI_vertex_attrib_array_object < GL_ATI_vertex_streams < GL_ATIX_texture_env_combine3 < GL_ATIX_texture_env_route < GL_ATIX_vertex_shader_output_point_size 61a71 > GL_EXT_blend_equation_separate 65a76,78 > GL_EXT_compiled_vertex_array > GL_EXT_convolution > GL_EXT_copy_texture 67,68c80 < GL_EXT_fog_coord < GL_EXT_multi_draw_arrays --- > GL_EXT_histogram 70c82 < GL_EXT_point_parameters --- > GL_EXT_polygon_offset 75c87,88 < GL_EXT_texgen_reflection --- > GL_EXT_subtexture > GL_EXT_texture 77,78d89 < GL_EXT_texture_compression_s3tc < GL_EXT_texture_cube_map 79a91 > GL_EXT_texture_env_add 88,90c100,109 < GL_EXT_vertex_shader < GL_HP_occlusion_test < GL_NV_texgen_reflection --- > GL_APPLE_packed_pixels > GL_ATI_blend_equation_separate > GL_ATI_texture_env_combine3 > GL_ATI_texture_mirror_once > GL_IBM_rasterpos_clip > GL_IBM_texture_mirrored_repeat > GL_INGR_blend_func_separate > GL_MESA_pack_invert > GL_MESA_ycbcr_texture > GL_MESA_window_pos 92c111,113 < GL_NV_occlusion_query --- > GL_NV_light_max_exponent > GL_NV_texture_rectangle > GL_NV_texgen_reflection 94c115,116 < GL_SGIS_texture_edge_clamp --- > GL_SGI_color_table > GL_SGIS_generate_mipmap 95a118 > GL_SGIS_texture_edge_clamp 97,98d119 < GL_SGIS_generate_mipmap < GL_SUN_multi_draw_arrays 107,126c128,143 < 0x25 24 tc 0 24 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow < 0x26 24 tc 0 24 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow < 0x27 24 tc 0 24 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow < 0x28 24 tc 0 24 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow < 0x29 24 tc 0 24 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None < 0x2a 24 tc 0 24 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None < 0x2b 24 tc 0 24 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None < 0x2c 24 tc 0 24 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None < 0x2d 24 dc 0 24 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow < 0x2e 24 dc 0 24 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow < 0x2f 24 dc 0 24 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow < 0x30 24 dc 0 24 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow < 0x31 24 dc 0 24 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None < 0x32 24 dc 0 24 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None < 0x33 24 dc
