headers
Michael Bergandi | 9 Aug 2011 17:33
Picon

diag_dump_*

Hi all,

I have been poking around looking at the diag_dump_* routines in
infra/current/src/diag.cxx and I see the following test in
diag_vdump_buf_with_offset() that makes me wonder what the intent was:

diag_vdump_buf_with_offset(__printf_fun *pf,
                           cyg_uint8     *p,
                           CYG_ADDRWORD   s,
                           cyg_uint8     *base)
{
    int i, c;
    if ((CYG_ADDRWORD)s > (CYG_ADDRWORD)p) {
        s = (CYG_ADDRWORD)s - (CYG_ADDRWORD)p;
    }

My understanding of the parameters are:

pf = pointer to function to use to print
p = pointer to buffer that you want to print
s = size (number of bytes to print)
base = base address to use for printing the addresses

I hope this is right. I can't find any documentation that actually
says what these parameters are. There is no documentation for the
function in diag.cxx, diag.hxx, or the reference manual.

So, the test above doesn't make much sense based on what I understand
the parameters to be.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gary Thomas | 9 Aug 2011 17:43
Favicon

Re: diag_dump_*

On 2011-08-09 09:33, Michael Bergandi wrote:
> Hi all,
>
> I have been poking around looking at the diag_dump_* routines in
> infra/current/src/diag.cxx and I see the following test in
> diag_vdump_buf_with_offset() that makes me wonder what the intent was:
>
> diag_vdump_buf_with_offset(__printf_fun *pf,
>                             cyg_uint8     *p,
>                             CYG_ADDRWORD   s,
>                             cyg_uint8     *base)
> {
>      int i, c;
>      if ((CYG_ADDRWORD)s>  (CYG_ADDRWORD)p) {
>          s = (CYG_ADDRWORD)s - (CYG_ADDRWORD)p;
>      }
>
> My understanding of the parameters are:
>
> pf = pointer to function to use to print
> p = pointer to buffer that you want to print
> s = size (number of bytes to print)
> base = base address to use for printing the addresses
>
> I hope this is right. I can't find any documentation that actually
> says what these parameters are. There is no documentation for the
> function in diag.cxx, diag.hxx, or the reference manual.
>
> So, the test above doesn't make much sense based on what I understand
> the parameters to be.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Arnaud Hubaux | 11 Aug 2011 16:03
Picon
Favicon

Study on conflict resolution with configtool

Dear eCos user, 

we are a team of researchers from the GSD Lab of the University of Waterloo (ON, Canada). We do research on
configuration methods and algorithms and are conducting a study on the problems faced by users during
conflict resolution with configtool. We would greatly appreciate it if you could answer the 17 questions
in the following questionnaire: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dDhrRmNVZ3NQMmMyNTU0RjBQOHg4eEE6MQ

The whole questionnaire should not take you more than 15 minutes to complete. 

Thank you very much for your contribution. 

Arnaud Hubaux, University of Namur/University of Waterloo
Yingfei Xiong, University of Waterloo
Permalink | Reply | 2 comments |
headers
Sergei Gavrikov | 13 Aug 2011 15:16
Picon

Verbose modes for eCos makefiles

Hi

I've written a few small patches to add a bit of sugar for eCos build
process when ``ecosconfig`` and ``make`` are used from command line.

Example:

  % ecosconfig new pid
  % ecosconfig tree
  % make
    GEN   mlt_arm_pid_ram.ldi
    GEN   mlt_arm_pid_rom.ldi
    GEN   mlt_arm_pid_ram.h
    GEN   mlt_arm_pid_rom.h
  headers finished
    GEN   ecos.mak
    GEN   arm.inc
    GEN   heapgeninc.tcl
    GEN   heaps.cxx
    CC    hal_misc.c
  ...
    CXX   errno.cxx
    AR    libtarget.a
    CC    vectors.S
    GEN   target.ld
  build finished

It was added a few checks for "V" variable (a verbose level) in eCos
``rules.mak`` file and the level of the verbosity is set in a top most
eCos ``makefile`` (which is auto-generated). The level of verbosity can
(Continue reading)

Permalink | Reply | 2 comments |
headers
Arnaud Hubaux | 13 Aug 2011 17:08
Picon
Favicon

Re: [ECOS] Study on conflict resolution with configtool

Dear eCos users,

several of you asked us whether the study is limited to configtool (GUI). The answer is no: it also includes
ecosconfig (command-line). If you have experience with either of them, your input is most welcome: https://docs.google.com/spreadsheet/viewform?formkey=dDhrRmNVZ3NQMmMyNTU0RjBQOHg4eEE6MQ

Thank you.

On 11 Aug 2011, at 10:03, Arnaud Hubaux wrote:

> Dear eCos user, 
> 
> we are a team of researchers from the GSD Lab of the University of Waterloo (ON, Canada). We do research on
configuration methods and algorithms and are conducting a study on the problems faced by users during
conflict resolution with configtool. We would greatly appreciate it if you could answer the 17 questions
in the following questionnaire: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dDhrRmNVZ3NQMmMyNTU0RjBQOHg4eEE6MQ
> 
> The whole questionnaire should not take you more than 15 minutes to complete. 
> 
> Thank you very much for your contribution. 
> 
> Arnaud Hubaux, University of Namur/University of Waterloo
> Yingfei Xiong, University of Waterloo 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 0 comments |
headers
John Dallaway | 21 Aug 2011 22:41
Picon

Re: Verbose modes for eCos makefiles

Hi Sergei

Sergei Gavrikov wrote:

> It was added a few checks for "V" variable (a verbose level) in eCos
> ``rules.mak`` file and the level of the verbosity is set in a top most
> eCos ``makefile`` (which is auto-generated). The level of verbosity can
> be set from a command line as ``make V=x`` where "x" can be set to 0, 1,
> or 2)
> 
>   V=0   - silent build (it is equal to a call ``make --silent``)
>   V=1   - "semi-silence", when ``make`` outputs a kind of work is
>           doing now
>   V=2   - full output (it is equal to "old" call of ``make``)
> 
> Default level is 1 (semi-silence). IMHO, it is right value and it is no
> need to type ``make V=1`` every time.
> 
> Pros (V=1):
> 
>   - He/she will be know what is running.
>   - He/she will be know/learn an order the build process.
>   - He/she will see any warnings and possible they will sent us the
>     patches to fix it :-)
> 
>   % make tests
>   ...
>     CC    strtoul.c
>     LINK  strtoul
>     CC    memchr.c
(Continue reading)

Permalink | Reply | 1 comment |
headers
Sergei Gavrikov | 22 Aug 2011 10:47
Picon

Re: Verbose modes for eCos makefiles

On Sun, 21 Aug 2011, John Dallaway wrote:

> Hi Sergei

Hi John,

> Sergei Gavrikov wrote:
> 
> > It was added a few checks for "V" variable (a verbose level) in eCos
> > ``rules.mak`` file and the level of the verbosity is set in a top most
> > eCos ``makefile`` (which is auto-generated). The level of verbosity can
> > be set from a command line as ``make V=x`` where "x" can be set to 0, 1,
> > or 2)
> > 
> >   V=0   - silent build (it is equal to a call ``make --silent``)
> >   V=1   - "semi-silence", when ``make`` outputs a kind of work is
> >           doing now
> >   V=2   - full output (it is equal to "old" call of ``make``)
> > 
> > Default level is 1 (semi-silence). IMHO, it is right value and it is no
> > need to type ``make V=1`` every time.
> > 
> > Pros (V=1):
> > 
> >   - He/she will be know what is running.
> >   - He/she will be know/learn an order the build process.
> >   - He/she will see any warnings and possible they will sent us the
> >     patches to fix it :-)
> > 
> >   % make tests
(Continue reading)

Permalink | Reply | 0 comments |

Gmane