<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en" style="--code-editor-font: var(--default-mono-font, "GitLab Mono"), JetBrains Mono, Menlo, DejaVu Sans Mono, Liberation Mono, Consolas, Ubuntu Mono, Courier New, andale mono, lucida console, monospace;">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title>
GitLab
</title>
<style data-premailer="ignore" type="text/css">
a { color: #1068bf; }
</style>
<style>img {
max-width: 100%; height: auto;
}
body {
font-size: .875rem;
}
body {
-webkit-text-shadow: rgba(255,255,255,.01) 0 0 1px;
}
body {
font-family: "GitLab Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji"; font-size: inherit;
}
</style>
</head>
<body style="font-size: inherit; -webkit-text-shadow: rgba(255,255,255,.01) 0 0 1px; font-family: "GitLab Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji";">
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.rtems.org/ppisa">Pavel Pisa</a>
commented on a
<a href="https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1209#note_149159">discussion</a>:
</p>
<div class="md" style="position: relative; z-index: 1; color: #3a383f; word-wrap: break-word;">
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial">I agree with manual fixup. The original generator was horrible and extremely tedious work solution (manually assisted OCR from PDF files, formatting and text flow has changed from chapter to chapter) because original Ti headers has incompatible license so they cannot be used even as the source for the generator for RTEMS style aligned headers. The Ti contributed to help situation to release headers under acceptable license later. It is seem that in some section the first comment character has failed repeatedly from the windows for OCR.</p>
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial">From the original workflow point, the right solution would be to update definitions in the raw OCR generated file</p>
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial"><a href="https://github.com/AoLaD/rtems-tms570-utils/tree/master/headers/raw_files" rel="nofollow noreferrer noopener" target="_blank" style="margin-top: 0;">https://github.com/AoLaD/rtems-tms570-utils/tree/master/headers/raw_files</a></p>
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial">But I expect, that even TMS570LC4357 support has been done by manual header files adjustments so reasonable regeneration is not possible anymore.</p>
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial">I think that the right way for today is to update generator to use CMSIS System View Description format(SVD) files, these are standard now, license should not be problem, they are in another language and are descriptive lists only. The example how to use them is for example there</p>
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial"><a href="https://github.com/robertlipe/svdtoheaders" rel="nofollow noreferrer noopener" target="_blank" style="margin-top: 0;">https://github.com/robertlipe/svdtoheaders</a></p>
<p dir="auto" style="color: #3a383f; margin: 0 0 1rem;" align="initial">But when the headers are regenerated (ideally by some unification from SVDs from all RTEMS supported and expected to be supported TMS570 family members) it would be necessary to check match with the current files.</p>
<p dir="auto" style="color: #3a383f; margin: 0;" align="initial">So I am for manual concretions for now.</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #626168;">
—
<br>
<a href="https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1209#note_149159">View it on GitLab</a>.
<br>
You're receiving this email because of your account on <a target="_blank" rel="noopener noreferrer" href="https://gitlab.rtems.org">gitlab.rtems.org</a>. <a href="https://gitlab.rtems.org/-/sent_notifications/3-cirbf33a1b3huhbl29sruvx4c/unsubscribe" target="_blank" rel="noopener noreferrer">Unsubscribe</a> from this thread · <a href="https://gitlab.rtems.org/-/profile/notifications" target="_blank" rel="noopener noreferrer" class="mng-notif-link">Manage all notifications</a> · <a href="https://gitlab.rtems.org/help" target="_blank" rel="noopener noreferrer" class="help-link">Help</a>
<span style="color: transparent; font-size: 0; display: none; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0;">
Notification message regarding https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1209#note_149159 at 1777365847
</span>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1209#note_149159"}}</script>
</p>
</div>
</body>
</html>