Saving content from TI Wiki

76 views
Skip to first unread message

din...@gmail.com

unread,
Oct 9, 2020, 5:01:28 PM10/9/20
to BeagleBoard
Dear Beagleboard.org overseers,

The TI Processors Wiki is being shutdown. I think valuable information would be lost that cannot be found in TRMs or Datasheets. For example, the following opcodes information was crucial while porting the GNU assembler for PRU:
https://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit

Are you willing to transfer that and similar content to beagleboard.org ? Wikimedia page sources can be mostly automatically translated to MarkDown or HTML. So content could be served   as a static page, with no need to host dynamic Wiki.

Regards,
Dimitar

Robert Nelson

unread,
Oct 9, 2020, 5:35:36 PM10/9/20
to Beagle Board

din...@gmail.com

unread,
Oct 10, 2020, 2:12:50 PM10/10/20
to BeagleBoard
On Saturday, October 10, 2020 at 12:35:36 AM UTC+3 RobertCNelson wrote:
On Fri, Oct 9, 2020 at 4:01 PM din...@gmail.com <din...@gmail.com> wrote:
>
> Dear Beagleboard.org overseers,
>
> The TI Processors Wiki is being shutdown. I think valuable information would be lost that cannot be found in TRMs or Datasheets. For example, the following opcodes information was crucial while porting the GNU assembler for PRU:
> https://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit
>
> Are you willing to transfer that and similar content to beagleboard.org ? Wikimedia page sources can be mostly automatically translated to MarkDown or HTML. So content could be served as a static page, with no need to host dynamic Wiki.


I don't think we could get access to that..
 
Wikimedia page source is still available: https://processors.wiki.ti.com/index.php?title=Programmable_Realtime_Unit&action=edit  . EOL is scheduled for December.

Jason Kridner

unread,
Oct 11, 2020, 5:08:39 PM10/11/20
to Beagle Board, Bill Traynor
I think TI would be supportive in giving us copies of relevant content. I barely got started copying content over to eLinux.org--that seems like the best host to me.

If you look at my latest contribution history (https://elinux.org/Special:Contributions/Jkridner), you can see a few pages I started to copy over to the Beagleboard space on elinux.org.

You can also see the assets didn't get moved over by me copying and pasting the text, obviously. I tried for a few minutes to think of a way to automate and didn't arrive at anything.

Remind me the next few days to provide the list I got on potential content. Then, others can add to that list if we missed anything. Mine is based on a spreadsheet I got from TI.

If anyone has good suggestions on automating the move, please let me know.


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0cf3f8f1-bcec-459d-ac02-a8b81773f118n%40googlegroups.com.


--
BeagleBoard.org Foundation is a US-based 501(c)3 non-profit providing education and collaboration around open source hardware and software

Use https://beagleboard.org/about/jkridner to schedule a meeting

Graham Stott

unread,
Oct 11, 2020, 5:49:10 PM10/11/20
to beagl...@googlegroups.com, Bill Traynor

Am I correct in assuming that we are talking about documentation? Also the older forums.  I presume that all software (compilers, SDKs, etc) will still be available.

 

I also started making a list. I will be interested to see your list(s)!

 

Graham

Reply all
Reply to author
Forward
0 new messages