Re: docs not building to PDF

[Sam Price]

I forgot the loop backs. from close back to open.

On Thu, Oct 13, 2022 at 1:12 AM Chris Johns  wrote:

> On 13/10/2022 4:06 pm, Sam Price wrote:
> > example
> >
> >
> https://mermaid.live/edit#pako:eNqFVG1vmzAQ_iuWP6UVaZM0DQGlkSYlnSJ1bUUyddmYkAlmYQEbGVP6sv732cdrtSrj0z0v9p19h1_xjgcU2ziTRNJFRH4JkvQfRy5zWcQi6WeBjVYqiEgcvVAUR76iSu2WyoKLwzu94lyWHBaRsNGOs0yi3Z4IdJrwnEkv5RGT6Aq5-FyGMnXxzBfnc0GzPNZ0cggi0UMdr4HW3sp5-PYV_amiz010dwKrdbWwAnK2e2mqh8CC9OdiFxsN7OZoSGez_LL2rlc3y_V2rWJvs71fepvrzf36iMlZflp4D85qs2xNLvZjvjtk6lquhoPR2CgiFvAC8Nh4pMLnGXVxWd6JPgJPKRPcRmGgitegh1Ii9wa685zF3e3NFimboES1xH-WNFMujXpqgYECIonn52FIhaHT6zw87HV5dFJvsItV7s5NAdb7aIPOXHxYxYNTV1GISNK2DIBtHQZkb3xHs-XQho6as6pv3XnRdSfBu-4C_sflMji8nmYUqkn0ynA202A-L2WEfpz-RP3-HFUzXtMVbKRmnFu5osACQ16LAEq6GsVGqTCIbVG1fIyBJeVc1GKJQNCtrGkdHyfh2rsKECCXTTiSvuhmL4CG1tY0gP_S7ypomQ9KKLOXnGreb9XetnkVDefSQ4ANnFCRkChQD9mrdrlY7mmi_i5bhQENiRoZ9fOzN2UlueTrZ7bDthQ5NXCeBu3Th-2QxJliU8K-c57UJgWx_YqfsD0cDs6soXk5mlyMR2PTmkwN_Kzo0dn4cmxZg4FlTqeTifVm4BfYQNkvLNMyzUvLvJhMp6b59hcqM78E
> <
> https://mermaid.live/edit#pako:eNqFVG1vmzAQ_iuWP6UVaZM0DQGlkSYlnSJ1bUUyddmYkAlmYQEbGVP6sv732cdrtSrj0z0v9p19h1_xjgcU2ziTRNJFRH4JkvQfRy5zWcQi6WeBjVYqiEgcvVAUR76iSu2WyoKLwzu94lyWHBaRsNGOs0yi3Z4IdJrwnEkv5RGT6Aq5-FyGMnXxzBfnc0GzPNZ0cggi0UMdr4HW3sp5-PYV_amiz010dwKrdbWwAnK2e2mqh8CC9OdiFxsN7OZoSGez_LL2rlc3y_V2rWJvs71fepvrzf36iMlZflp4D85qs2xNLvZjvjtk6lquhoPR2CgiFvAC8Nh4pMLnGXVxWd6JPgJPKRPcRmGgitegh1Ii9wa685zF3e3NFimboES1xH-WNFMujXpqgYECIonn52FIhaHT6zw87HV5dFJvsItV7s5NAdb7aIPOXHxYxYNTV1GISNK2DIBtHQZkb3xHs-XQho6as6pv3XnRdSfBu-4C_sflMji8nmYUqkn0ynA202A-L2WEfpz-RP3-HFUzXtMVbKRmnFu5osACQ16LAEq6GsVGqTCIbVG1fIyBJeVc1GKJQNCtrGkdHyfh2rsKECCXTTiSvuhmL4CG1tY0gP_S7ypomQ9KKLOXnGreb9XetnkVDefSQ4ANnFCRkChQD9mrdrlY7mmi_i5bhQENiRoZ9fOzN2UlueTrZ7bDthQ5NXCeBu3Th-2QxJliU8K-c57UJgWx_YqfsD0cDs6soXk5mlyMR2PTmkwN_Kzo0dn4cmxZg4FlTqeTifVm4BfYQNkvLNMyzUvLvJhMp6b59hcqM78E
> >
> >
> > SVG link
> >
> https://mermaid.ink/svg/pako:eNqFVG1v2jAQ_iuWP0GVtrxDIoo0CTohdaUCJsaWKXKIMzKIjRynKWX899mXV7SK5dM9L_adfRef8IZ7FFs4kkTScUB-CRLevrZsZrOABdKNPAtNVRCQffBO0T5wFZVqz1QmXOwu9IyzWbgbB8JCG84iiTZbItBNyGMmnQMPmEQPyMb30pcHGw9dcT8SNIr3mg53XiBqqOI10MKZzlffvqI_WfS5iGZ1WK2rhRWQs9xLUzUEFqQ_G9vYKGA1R0HOl5MvC-dx-jRZrBcqdpbrl4mzfFy-LK6Y5pNPY2c1ny4npcnG7p5vdpG6lodmo9UxkoB5PAHcMV6pcHlEbZyWV9dH4AfKBLeQ76niNaihA5FbA82c-Xj2_LRGyiYoUS1xj5JGyqVRTS0wkEckcdzY96kwdHqdh_u1Ko_q-QabvcpduSnAeh9t0JmTD6tYzfMqEhFIWpYBsKzDgOyF72q2GNpQUWOW9a06L7ru0LvoLuB_XDaDw-tpRr6aRCcNh0MNRqNURujHzU90eztC2YzndAYLqRjnUs4osMCQ5yKAlM5GsVAyDGJZVC5fY2BJOhe5mCIQdCtzWsfXSbj2qgIEyGkTrqRPqtkToKG1OQ3gv_RFBSXzQQlp9pRTzfut2ls2L6PhXHoIsIFDKkISeOohO2mXjeWWhurvslToUZ-okVE_PzsrK4klXxzZBltSxNTA8cErn76cPBD2nfMqxNYJv2Gr2Wzcmc1-t9Vrd1qdvtkbGPio6NZdp9sxzUbD7A8GvZ55NvA7bKDsbbNv9vtds9HtNcxm-_wXZ4G-ow
> <
> https://mermaid.ink/svg/pako:eNqFVG1v2jAQ_iuWP0GVtrxDIoo0CTohdaUCJsaWKXKIMzKIjRynKWX899mXV7SK5dM9L_adfRef8IZ7FFs4kkTScUB-CRLevrZsZrOABdKNPAtNVRCQffBO0T5wFZVqz1QmXOwu9IyzWbgbB8JCG84iiTZbItBNyGMmnQMPmEQPyMb30pcHGw9dcT8SNIr3mg53XiBqqOI10MKZzlffvqI_WfS5iGZ1WK2rhRWQs9xLUzUEFqQ_G9vYKGA1R0HOl5MvC-dx-jRZrBcqdpbrl4mzfFy-LK6Y5pNPY2c1ny4npcnG7p5vdpG6lodmo9UxkoB5PAHcMV6pcHlEbZyWV9dH4AfKBLeQ76niNaihA5FbA82c-Xj2_LRGyiYoUS1xj5JGyqVRTS0wkEckcdzY96kwdHqdh_u1Ko_q-QabvcpduSnAeh9t0JmTD6tYzfMqEhFIWpYBsKzDgOyF72q2GNpQUWOW9a06L7ru0LvoLuB_XDaDw-tpRr6aRCcNh0MNRqNURujHzU90eztC2YzndAYLqRjnUs4osMCQ5yKAlM5GsVAyDGJZVC5fY2BJOhe5mCIQdCtzWsfXSbj2qgIEyGkTrqRPqtkToKG1OQ3gv_RFBSXzQQlp9pRTzfut2ls2L6PhXHoIsIFDKkISeOohO2mXjeWWhurvslToUZ-okVE_PzsrK4klXxzZBltSxNTA8cErn76cPBD2nfMqxNYJv2Gr2Wzcmc1-t9Vrd1qdvtkbGPio6NZdp9sxzUbD7A8GvZ55NvA7bKDsbbNv9vtds9HtNcxm-_wXZ4G-ow
> >
> >
> >
> > I couldn't figure out how to get semi colons to work
> > new lines are kind  of a pain also.
>
> You are a legend (pun intended) :D
>
> It is looking goo but Frank has the final say.
>
> Chris
>
> >
> > stateDiagram-v2
> >
> > initbsd:Initialize libbsd
> > initNetwork:Initialize Network
> > mkDir:const char *mount_point = "/tftp"result = mkdir( mount_point,
> S_IRWXU
> > | S_IRWXG | S_IRWXO)
> >
> > mountDir:result = mount(  "", mount_point,
> > RTEMS_FILESYSTEM_TYPE_TFTPS, RTEMS_FILESYSTEM_READ_WRITE,
> > "blocksize=1024,windowsize=4,verbose" )
> >
> > openro:fd = open( path, O_RDONLY )
> > read:bytes = read( fd, data_buffer, sizeof( data_buffer ) )
> > readclose:result = close( fd )
> > openw:fd = open( path, O_WRONLY )
> > write:bytes = write( fd, data, size )
> > writeclose:result = close( fd )
> > umount:result = unmount( mount_point )
> > rmdir:result = rmdir( mount_point )
> >
> > state fork_state <>
> > [*] --> initbsd
> > initbsd --> initNetwork
> > initNetwork --> mkDir
> > mkDir --> mountDir
> > mountDir --> fork_state
> > fork_state
> > fork_state --> openro
> > openro --> read
> > read --> read
> > read --> readclose
> > readclose --> umount
> > fork_state --> openw
> > openw --> write
> > write --> write
> > write --> writeclose
> > writeclose --> umount
> > state umount <>
> > umount --> rmdir
> >
>


-- 
Sincerely,

Sam Price

Re: docs not building to PDF

[Chris Johns]

On 13/10/2022 4:06 pm, Sam Price wrote:
> example
> 
> https://mermaid.live/edit#pako:eNqFVG1vmzAQ_iuWP6UVaZM0DQGlkSYlnSJ1bUUyddmYkAlmYQEbGVP6sv732cdrtSrj0z0v9p19h1_xjgcU2ziTRNJFRH4JkvQfRy5zWcQi6WeBjVYqiEgcvVAUR76iSu2WyoKLwzu94lyWHBaRsNGOs0yi3Z4IdJrwnEkv5RGT6Aq5-FyGMnXxzBfnc0GzPNZ0cggi0UMdr4HW3sp5-PYV_amiz010dwKrdbWwAnK2e2mqh8CC9OdiFxsN7OZoSGez_LL2rlc3y_V2rWJvs71fepvrzf36iMlZflp4D85qs2xNLvZjvjtk6lquhoPR2CgiFvAC8Nh4pMLnGXVxWd6JPgJPKRPcRmGgitegh1Ii9wa685zF3e3NFimboES1xH-WNFMujXpqgYECIonn52FIhaHT6zw87HV5dFJvsItV7s5NAdb7aIPOXHxYxYNTV1GISNK2DIBtHQZkb3xHs-XQho6as6pv3XnRdSfBu-4C_sflMji8nmYUqkn0ynA202A-L2WEfpz-RP3-HFUzXtMVbKRmnFu5osACQ16LAEq6GsVGqTCIbVG1fIyBJeVc1GKJQNCtrGkdHyfh2rsKECCXTTiSvuhmL4CG1tY0gP_S7ypomQ9KKLOXnGreb9XetnkVDefSQ4ANnFCRkChQD9mrdrlY7mmi_i5bhQENiRoZ9fOzN2UlueTrZ7bDthQ5NXCeBu3Th-2QxJliU8K-c57UJgWx_YqfsD0cDs6soXk5mlyMR2PTmkwN_Kzo0dn4cmxZg4FlTqeTifVm4BfYQNkvLNMyzUvLvJhMp6b59hcqM78E
>  
> 
> 
> SVG link
> https://mermaid.ink/svg/pako:eNqFVG1v2jAQ_iuWP0GVtrxDIoo0CTohdaUCJsaWKXKIMzKIjRynKWX899mXV7SK5dM9L_adfRef8IZ7FFs4kkTScUB-CRLevrZsZrOABdKNPAtNVRCQffBO0T5wFZVqz1QmXOwu9IyzWbgbB8JCG84iiTZbItBNyGMmnQMPmEQPyMb30pcHGw9dcT8SNIr3mg53XiBqqOI10MKZzlffvqI_WfS5iGZ1WK2rhRWQs9xLUzUEFqQ_G9vYKGA1R0HOl5MvC-dx-jRZrBcqdpbrl4mzfFy-LK6Y5pNPY2c1ny4npcnG7p5vdpG6lodmo9UxkoB5PAHcMV6pcHlEbZyWV9dH4AfKBLeQ76niNaihA5FbA82c-Xj2_LRGyiYoUS1xj5JGyqVRTS0wkEckcdzY96kwdHqdh_u1Ko_q-QabvcpduSnAeh9t0JmTD6tYzfMqEhFIWpYBsKzDgOyF72q2GNpQUWOW9a06L7ru0LvoLuB_XDaDw-tpRr6aRCcNh0MNRqNURujHzU90eztC2YzndAYLqRjnUs4osMCQ5yKAlM5GsVAyDGJZVC5fY2BJOhe5mCIQdCtzWsfXSbj2qgIEyGkTrqRPqtkToKG1OQ3gv_RFBSXzQQlp9pRTzfut2ls2L6PhXHoIsIFDKkISeOohO2mXjeWWhurvslToUZ-okVE_PzsrK4klXxzZBltSxNTA8cErn76cPBD2nfMqxNYJv2Gr2Wzcmc1-t9Vrd1qdvtkbGPio6NZdp9sxzUbD7A8GvZ55NvA7bKDsbbNv9vtds9HtNcxm-_wXZ4G-ow
>  
> 
> 
> 
> I couldn't figure out how to get semi colons to work
> new lines are kind  of a pain also.

You are a legend (pun intended) :D

It is looking goo but Frank has the final say.

Chris

> 
> stateDiagram-v2
> 
> initbsd:Initialize libbsd
> initNetwork:Initialize Network
> mkDir:const char *mount_point = "/tftp"result = mkdir( mount_point, 
> S_IRWXU
> | S_IRWXG | S_IRWXO)
> 
> mountDir:result = mount(  "", mount_point,
> RTEMS_FILESYSTEM_TYPE_TFTPS, RTEMS_FILESYSTEM_READ_WRITE,
> "blocksize=1024,windowsize=4,verbose" )
> 
> openro:fd = open( path, O_RDONLY )
> read:bytes = read( fd, data_buffer, sizeof( data_buffer ) )
> readclose:result = close( fd )
> openw:fd = open( path, O_WRONLY )
> write:bytes = write( fd, data, size )
> writeclose:result = close( fd )
> umount:result = unmount( mount_point )
> rmdir:result = rmdir( mount_point )
> 
> state fork_state <>
> [*] --> initbsd
> initbsd --> initNetwork
> initNetwork --> mkDir
> mkDir --> mountDir
> mountDir --> fork_state
> fork_state
> fork_state --> openro
> openro --> read
> read --> read
> read --> readclose
> readclose --> umount
> fork_state --> openw
> openw --> write
> write --> write
> write --> writeclose
> writeclose --> umount
> state umount <>
> umount --> rmdir
> 
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Sam Price]

example

https://mermaid.live/edit#pako:eNqFVG1vmzAQ_iuWP6UVaZM0DQGlkSYlnSJ1bUUyddmYkAlmYQEbGVP6sv732cdrtSrj0z0v9p19h1_xjgcU2ziTRNJFRH4JkvQfRy5zWcQi6WeBjVYqiEgcvVAUR76iSu2WyoKLwzu94lyWHBaRsNGOs0yi3Z4IdJrwnEkv5RGT6Aq5-FyGMnXxzBfnc0GzPNZ0cggi0UMdr4HW3sp5-PYV_amiz010dwKrdbWwAnK2e2mqh8CC9OdiFxsN7OZoSGez_LL2rlc3y_V2rWJvs71fepvrzf36iMlZflp4D85qs2xNLvZjvjtk6lquhoPR2CgiFvAC8Nh4pMLnGXVxWd6JPgJPKRPcRmGgitegh1Ii9wa685zF3e3NFimboES1xH-WNFMujXpqgYECIonn52FIhaHT6zw87HV5dFJvsItV7s5NAdb7aIPOXHxYxYNTV1GISNK2DIBtHQZkb3xHs-XQho6as6pv3XnRdSfBu-4C_sflMji8nmYUqkn0ynA202A-L2WEfpz-RP3-HFUzXtMVbKRmnFu5osACQ16LAEq6GsVGqTCIbVG1fIyBJeVc1GKJQNCtrGkdHyfh2rsKECCXTTiSvuhmL4CG1tY0gP_S7ypomQ9KKLOXnGreb9XetnkVDefSQ4ANnFCRkChQD9mrdrlY7mmi_i5bhQENiRoZ9fOzN2UlueTrZ7bDthQ5NXCeBu3Th-2QxJliU8K-c57UJgWx_YqfsD0cDs6soXk5mlyMR2PTmkwN_Kzo0dn4cmxZg4FlTqeTifVm4BfYQNkvLNMyzUvLvJhMp6b59hcqM78E

SVG link
https://mermaid.ink/svg/pako:eNqFVG1v2jAQ_iuWP0GVtrxDIoo0CTohdaUCJsaWKXKIMzKIjRynKWX899mXV7SK5dM9L_adfRef8IZ7FFs4kkTScUB-CRLevrZsZrOABdKNPAtNVRCQffBO0T5wFZVqz1QmXOwu9IyzWbgbB8JCG84iiTZbItBNyGMmnQMPmEQPyMb30pcHGw9dcT8SNIr3mg53XiBqqOI10MKZzlffvqI_WfS5iGZ1WK2rhRWQs9xLUzUEFqQ_G9vYKGA1R0HOl5MvC-dx-jRZrBcqdpbrl4mzfFy-LK6Y5pNPY2c1ny4npcnG7p5vdpG6lodmo9UxkoB5PAHcMV6pcHlEbZyWV9dH4AfKBLeQ76niNaihA5FbA82c-Xj2_LRGyiYoUS1xj5JGyqVRTS0wkEckcdzY96kwdHqdh_u1Ko_q-QabvcpduSnAeh9t0JmTD6tYzfMqEhFIWpYBsKzDgOyF72q2GNpQUWOW9a06L7ru0LvoLuB_XDaDw-tpRr6aRCcNh0MNRqNURujHzU90eztC2YzndAYLqRjnUs4osMCQ5yKAlM5GsVAyDGJZVC5fY2BJOhe5mCIQdCtzWsfXSbj2qgIEyGkTrqRPqtkToKG1OQ3gv_RFBSXzQQlp9pRTzfut2ls2L6PhXHoIsIFDKkISeOohO2mXjeWWhurvslToUZ-okVE_PzsrK4klXxzZBltSxNTA8cErn76cPBD2nfMqxNYJv2Gr2Wzcmc1-t9Vrd1qdvtkbGPio6NZdp9sxzUbD7A8GvZ55NvA7bKDsbbNv9vtds9HtNcxm-_wXZ4G-ow


I couldn't figure out how to get semi colons to work
new lines are kind  of a pain also.

stateDiagram-v2

initbsd: Initialize libbsd
initNetwork: Initialize Network
mkDir: const char *mount_point = "/tftp"result = mkdir( mount_point,
S_IRWXU | S_IRWXG | S_IRWXO)

mountDir: result = mount(  "", mount_point,
RTEMS_FILESYSTEM_TYPE_TFTPS, RTEMS_FILESYSTEM_READ_WRITE,
"blocksize=1024,windowsize=4,verbose" )

openro: fd = open( path, O_RDONLY )
read: bytes = read( fd, data_buffer, sizeof( data_buffer ) )
readclose: result = close( fd )
openw: fd = open( path, O_WRONLY )
write: bytes = write( fd, data, size )
writeclose: result = close( fd )
umount: result = unmount( mount_point )
rmdir: result = rmdir( mount_point )

state fork_state <>
[*] --> initbsd
initbsd --> initNetwork
initNetwork --> mkDir
mkDir --> mountDir
mountDir --> fork_state
fork_state
fork_state --> openro
openro --> read
read --> read
read --> readclose
readclose --> umount
fork_state --> openw
openw --> write
write --> write
write --> writeclose
writeclose --> umount
state umount <>
umount --> rmdir
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Visibility of RISCV_BOOT_HARTID

[Sebastian Huber]

On 12/10/2022 16:36, Joel Sherrill wrote:

Hi

I was looking at the bsp default settings for sparc/leon3 to show 
someone and noticed this which is out of place.


# boot hartid (processor number) of risc-v cpu (default 0)
RISCV_BOOT_HARTID = 0

I looked around and see it is an architecture specific ini setting but 
placed in a directory with architecture independent settings. We don't 
appear to have any other examples of a cpukit option that is 
architecture specific. So it is lumped in with all the architecture 
independent ini settings.


This was easy to fix:

https://git.rtems.org/rtems/commit/?id=97fce5120c08180a86301b03e61d0a06db5f8b9b



We had long discussions about presenting these options with better 
names, documentation, etc as part of the waf transition. Seems 
unfortunate to have this show up in all configurations.


Any thoughts on how to clean this up?


It would be nice if more developers could invest some time to learn how 
the build system works.


--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Chris Johns]

On 13/10/2022 3:15 pm, Sam Price wrote:
> Yes
> https://github.com/mermaid-js/mermaid-cli
> 
> 
> There are command line tools so it can be integrated into pipelines.
> 
> 
>   Convert Mermaid mmd Diagram File To SVG
> 
> mmdc -i input.mmd -o output.svg
> 
> 
>   
> Create
>  A PNG With A Dark Theme And Transparent Background
> 
> mmdc -i input.mmd -o output.png -t dark -b transparent
> 
> You dont get much control though over how it places boxes. 
> But it does sequence diagrams.
> Im using it for gantt charts.
> 
> Its one of the mainstream alternatives to plantuml
> 

This tool looks really good and it fits the pattern of tools we can use.

Thanks for this.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Sam Price]

Yes
https://github.com/mermaid-js/mermaid-cli

There are command line tools so it can be integrated into pipelines.
Convert Mermaid mmd Diagram File To SVG

mmdc -i input.mmd -o output.svg

Create
A PNG With A Dark Theme And Transparent Background

mmdc -i input.mmd -o output.png -t dark -b transparent

You dont get much control though over how it places boxes.
But it does sequence diagrams.
Im using it for gantt charts.

Its one of the mainstream alternatives to plantuml
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Chris Johns]

On 13/10/2022 2:01 pm, Sam Price wrote:
> Have you guys looked at mermaidjs for simplistic diagrams?
> https://mermaid-js.github.io/mermaid/#/flowchart
> 

No I have not.

> You can embed it in markdown. pandoc will convert it to images for html.
> it works on gitlab wiki, and prob others.

Can it generate a format we can embed in PDFs?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Sam Price]

Have you guys looked at mermaidjs for simplistic diagrams?
https://mermaid-js.github.io/mermaid/#/flowchart

You can embed it in markdown. pandoc will convert it to images for html.
it works on gitlab wiki, and prob others.

On Wed, Oct 12, 2022 at 8:31 PM Chris Johns  wrote:

>
>
> On 12/10/2022 8:56 pm, Frank Kühndel wrote:
> > Hello Chris,
> > On 10/11/22 23:47, Chris Johns wrote:
> >> On 11/10/2022 7:12 pm, Frank Kühndel wrote:
> >>> Hello Chris,
> >>>
> >>> On 10/11/22 03:09, Chris Johns wrote:
>  On 10/10/2022 9:22 pm, Frank Kühndel wrote:
> > images/filesystem/tftpfs_usage.png:
> > https://share.embedded-brains.de/index.php/s/fQ4WrLrqmBjcbwC
>  I have a greyed out image I cannot clearly see?
> >>> The image has a transparent background. Some image viewers put a gray
> pattern in
> >>> the background in those case. The PDF has naturally a white background
> on top of
> >>> which the image is displayed.
> >>>
> > images/filesystem/ftpfs_usage.svg:
> > https://share.embedded-brains.de/index.php/s/xk7kArkm6mbjcn2
> >
> > The SVG file is the source for the PNG. Both files must be placed in
> the
> > images/filesystem folder.
>  How is the SVG file created and how can it be edited?
> >>> I used Inkscape. It should be possible to edit it with (almost) any
> tool that
> >>> supports SVG.
> >> I tried withhttps://pixelied.com/features/svg-editor  and it was a
> mess.
> >
> > Yes. I tried another Web-based tool and it was the same mess. Yet, all
> converter
> > handle this correctly. For example:
> >
> > $ firefox file:///home/frank/tftpfs_usage.svg
> > $ convert -geometry 1422x1574 tftpfs_usage.svg tftpfs_usage.png
> > $ display tftpfs_usage.svg
> > $ libreoffice tftpfs_usage.svg
> > $ rsvg-convert --width 1422 --height 1574 -o tftpfs_usage_Z.png
> tftpfs_usage.svg
> >
> > So, I guess it is a bug in the web-based tools.
>
> The format is always going to be fragile and locked into the specific tool
> used
> to create it. Being an open format does not help. Word is a form of XML
> and it
> is also not suitable.
>
> >> My concern is the widgets (or whatever they are called) a tool has may
> not be
> >> available in another.
> >
> > Inkscape is open source and available freely on (almost?) all operating
> system.
> > It is *the* standard open source tool for producing high-quality vector
> graphics
> > today.
>
> I do not agree and I question "the" in your last sentence. Making a fact
> of your
> view does not impress me.
>
> We need a solution that can be maintained past your current employment.
>
> >>> Your Web-Browser should be able to display SVG directly when you
> >>> point it to the file like for
> example:file:///home//tftpfs_usage.svg
> >>>
> >>> You can recreate the PNG with Inkscape on the command line with:
> >>>
> >>> $ inkscape --export-dpi=300 --export-filename=tftpfs_usage.png
> tftpfs_usage.svg
> >> We have a number of images in the doco created using PlantUML. Did you
> consider
> >> using that tool? It has the advantage the images can be regenerated
> from the
> >> source as part of the build if PlantUML and Ditaa are installed and we
> get a
> >> consistent looking set of images.
> >
> > I took a look into PlantUML:
> >
> > * My image is not an UML diagram (or similar to another diagram input
> format it
> > supports)
>
> Ditaa is an option and easy to use.
>
> > * It may be realized as an Activity Diagram, yet. But it will not look
> very
> > similar to the current image.
> >
> > * Most of all, I will need to spend significant time to learn PlantUML
> and to
> > get the result in shape I will certainly need to do some trying and
> fumbling
> > around.
>
> Maybe an example would help:
>
>
> https://git.rtems.org/rtems-docs/tree/images/user/exe-debug-libdebugger.ditaa
>
> > Openly, my company will never pay me for converting the image to
> PlantUML. Sorry
> > about this.
>
> Seems you have made this a commercial issue on a public mailing list I have
> included Thomas on the email and he can reach out me directly. I always
> enjoy
> catching up with him.
>
> > Do you see any solution to this problem?
>
> 1. Revert the patch.
>
> 2. Use something like ditaa
>
> 3. Reword the section to not include the image
>
> In the mean time the docs are not building.
>
> Chris
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel



-- 
Sincerely,

Sam Price
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] README: Add a note about image tools

[chrisj]

From: Chris Johns 

---
 README.txt | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/README.txt b/README.txt
index 07bae0d..e9bf966 100644
--- a/README.txt
+++ b/README.txt
@@ -90,6 +90,21 @@ You do not need PlantUML or Ditaa installed to build our 
documentation. The
 online resources can be used. Save the source and the generated PNG file in the
 same directory under 'images'.
 
+*Note:*
+Please consider using PlantUML and Ditaa before other tools because we
+can generate the images from source automatically and it gives the
+documentation a similar look and feel. Other options may be considered
+if the image cannot be easly created by PlantUML or Ditaa but please
+ask before starting down that path because it may not be accepted.
+
+Image editing tools tend to have a specific look and feel and this
+characterizes the images they create. Altering an image often means
+the original tool is required. An open output format allows us to
+integrate the image into the document however we are then required to
+monitor and maintain that tool if we need to make changes. The fewer
+alternatives we have to maintain the easier it is for the project over
+a long period of time.
+
 Host Setup
 --
 
-- 
2.37.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Cygwin tools failure

[Chris Johns]

On 12/10/2022 3:24 pm, Chris Johns wrote:
> Consider a patch to add the piece removed at the end of this patch as 
> approved.

I see the patch was pushed, thanks. The RSB hash will need to be updated so
users pick it up.

Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Chris Johns]

On 12/10/2022 8:56 pm, Frank Kühndel wrote:
> Hello Chris,
> On 10/11/22 23:47, Chris Johns wrote:
>> On 11/10/2022 7:12 pm, Frank Kühndel wrote:
>>> Hello Chris,
>>>
>>> On 10/11/22 03:09, Chris Johns wrote:
 On 10/10/2022 9:22 pm, Frank Kühndel wrote:
> images/filesystem/tftpfs_usage.png:
> https://share.embedded-brains.de/index.php/s/fQ4WrLrqmBjcbwC
 I have a greyed out image I cannot clearly see?
>>> The image has a transparent background. Some image viewers put a gray 
>>> pattern in
>>> the background in those case. The PDF has naturally a white background on 
>>> top of
>>> which the image is displayed.
>>>
> images/filesystem/ftpfs_usage.svg:
> https://share.embedded-brains.de/index.php/s/xk7kArkm6mbjcn2
>
> The SVG file is the source for the PNG. Both files must be placed in the
> images/filesystem folder.
 How is the SVG file created and how can it be edited?
>>> I used Inkscape. It should be possible to edit it with (almost) any tool 
>>> that
>>> supports SVG.
>> I tried withhttps://pixelied.com/features/svg-editor  and it was a mess.
> 
> Yes. I tried another Web-based tool and it was the same mess. Yet, all 
> converter
> handle this correctly. For example:
> 
> $ firefox file:///home/frank/tftpfs_usage.svg
> $ convert -geometry 1422x1574 tftpfs_usage.svg tftpfs_usage.png
> $ display tftpfs_usage.svg
> $ libreoffice tftpfs_usage.svg
> $ rsvg-convert --width 1422 --height 1574 -o tftpfs_usage_Z.png 
> tftpfs_usage.svg
> 
> So, I guess it is a bug in the web-based tools.

The format is always going to be fragile and locked into the specific tool used
to create it. Being an open format does not help. Word is a form of XML and it
is also not suitable.

>> My concern is the widgets (or whatever they are called) a tool has may not be
>> available in another.
> 
> Inkscape is open source and available freely on (almost?) all operating 
> system.
> It is *the* standard open source tool for producing high-quality vector 
> graphics
> today.

I do not agree and I question "the" in your last sentence. Making a fact of your
view does not impress me.

We need a solution that can be maintained past your current employment.

>>> Your Web-Browser should be able to display SVG directly when you
>>> point it to the file like for 
>>> example:file:///home//tftpfs_usage.svg
>>>
>>> You can recreate the PNG with Inkscape on the command line with:
>>>
>>> $ inkscape --export-dpi=300 --export-filename=tftpfs_usage.png 
>>> tftpfs_usage.svg
>> We have a number of images in the doco created using PlantUML. Did you 
>> consider
>> using that tool? It has the advantage the images can be regenerated from the
>> source as part of the build if PlantUML and Ditaa are installed and we get a
>> consistent looking set of images.
> 
> I took a look into PlantUML:
> 
> * My image is not an UML diagram (or similar to another diagram input format 
> it
> supports)

Ditaa is an option and easy to use.

> * It may be realized as an Activity Diagram, yet. But it will not look very
> similar to the current image.
>
> * Most of all, I will need to spend significant time to learn PlantUML and to
> get the result in shape I will certainly need to do some trying and fumbling
> around.

Maybe an example would help:

https://git.rtems.org/rtems-docs/tree/images/user/exe-debug-libdebugger.ditaa

> Openly, my company will never pay me for converting the image to PlantUML. 
> Sorry
> about this.

Seems you have made this a commercial issue on a public mailing list I have
included Thomas on the email and he can reach out me directly. I always enjoy
catching up with him.

> Do you see any solution to this problem?

1. Revert the patch.

2. Use something like ditaa

3. Reword the section to not include the image

In the mean time the docs are not building.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

RE: Visibility of RISCV_BOOT_HARTID

[Alan Cudmore]

Hi Joel,This is relevant to my interests since I am working on a RISC-V BSP variant and I am adding a few options in the spec/build/bsps/riscv/riscv directory.Could this instance be fixed by moving it to the spec/build/bsps/riscv directory?Regards,AlanFrom: Joel SherrillSent: Wednesday, October 12, 2022 10:36 AMTo: rtems-de...@rtems.orgSubject: Visibility of RISCV_BOOT_HARTID Hi I was looking at the bsp default settings for sparc/leon3 to show someone and noticed this which is out of place.  # boot hartid (processor number) of risc-v cpu (default 0)RISCV_BOOT_HARTID = 0 I looked around and see it is an architecture specific ini setting but placed in a directory with architecture independent settings. We don't appear to have any other examples of a cpukit option that is architecture specific. So it is lumped in with all the architecture independent ini settings. We had long discussions about presenting these options with better names, documentation, etc as part of the waf transition. Seems unfortunate to have this show up in all configurations. Any thoughts on how to clean this up? Thanks. --joel   
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Visibility of RISCV_BOOT_HARTID

[Joel Sherrill]

Hi

I was looking at the bsp default settings for sparc/leon3 to show someone
and noticed this which is out of place.

# boot hartid (processor number) of risc-v cpu (default 0)
RISCV_BOOT_HARTID = 0

I looked around and see it is an architecture specific ini setting but
placed in a directory with architecture independent settings. We don't
appear to have any other examples of a cpukit option that is architecture
specific. So it is lumped in with all the architecture independent ini
settings.

We had long discussions about presenting these options with better names,
documentation, etc as part of the waf transition. Seems unfortunate to have
this show up in all configurations.

Any thoughts on how to clean this up?

Thanks.

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] bsp-howto: Specify name of clock driver init func

[Matthew Joyce]

From: Matt Joyce 

---
 bsp-howto/clock.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bsp-howto/clock.rst b/bsp-howto/clock.rst
index f3d30ce..b03f5ce 100644
--- a/bsp-howto/clock.rst
+++ b/bsp-howto/clock.rst
@@ -65,7 +65,7 @@ Clock Tick Only
 Initialization
 ==
 
-The clock driver is initialized by a dedicated system initialization handler if
+The clock driver is initialized by the ``_Clock_Initialize()`` handler if
 requested by the application configuration option
 ``CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER``.  The clock driver does not use 
the
 legacy IO driver framework.
-- 
2.31.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Frank Kühndel]

Hello Chris,

On 10/11/22 23:47, Chris Johns wrote:

On 11/10/2022 7:12 pm, Frank Kühndel wrote:

Hello Chris,

On 10/11/22 03:09, Chris Johns wrote:

On 10/10/2022 9:22 pm, Frank Kühndel wrote:

images/filesystem/tftpfs_usage.png:
https://share.embedded-brains.de/index.php/s/fQ4WrLrqmBjcbwC

I have a greyed out image I cannot clearly see?

The image has a transparent background. Some image viewers put a gray pattern in
the background in those case. The PDF has naturally a white background on top of
which the image is displayed.


images/filesystem/ftpfs_usage.svg:
https://share.embedded-brains.de/index.php/s/xk7kArkm6mbjcn2

The SVG file is the source for the PNG. Both files must be placed in the
images/filesystem folder.

How is the SVG file created and how can it be edited?

I used Inkscape. It should be possible to edit it with (almost) any tool that
supports SVG.

I tried withhttps://pixelied.com/features/svg-editor  and it was a mess.


Yes. I tried another Web-based tool and it was the same mess. Yet, all 
converter handle this correctly. For example:


$ firefox file:///home/frank/tftpfs_usage.svg
$ convert -geometry 1422x1574 tftpfs_usage.svg tftpfs_usage.png
$ display tftpfs_usage.svg
$ libreoffice tftpfs_usage.svg
$ rsvg-convert --width 1422 --height 1574 -o tftpfs_usage_Z.png 
tftpfs_usage.svg


So, I guess it is a bug in the web-based tools.



My concern is the widgets (or whatever they are called) a tool has may not be
available in another.


Inkscape is open source and available freely on (almost?) all operating 
system. It is *the* standard open source tool for producing high-quality 
vector graphics today.





Your Web-Browser should be able to display SVG directly when you
point it to the file like for example:file:///home//tftpfs_usage.svg

You can recreate the PNG with Inkscape on the command line with:

$ inkscape --export-dpi=300 --export-filename=tftpfs_usage.png tftpfs_usage.svg

We have a number of images in the doco created using PlantUML. Did you consider
using that tool? It has the advantage the images can be regenerated from the
source as part of the build if PlantUML and Ditaa are installed and we get a
consistent looking set of images.


I took a look into PlantUML:

* My image is not an UML diagram (or similar to another diagram input 
format it supports)
* It may be realized as an Activity Diagram, yet. But it will not look 
very similar to the current image.
* Most of all, I will need to spend significant time to learn PlantUML 
and to get the result in shape I will certainly need to do some trying 
and fumbling around.


Openly, my company will never pay me for converting the image to 
PlantUML. Sorry about this.


Do you see any solution to this problem?

Greetings
Frank

--
embedded brains GmbH
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11
fax:+49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel