View source for User talk:Wmat
SSL
Hi, it would be nice to have SSL support (at least for login) on elinux.org. Currently https://elinux.org returns "You don't have permission to access / on this server." using a certificate for "*.osuosl.org". Thanks for considering.
- [View source↑]
- [History↑]
Contents
Thread title | Replies | Last modified |
---|---|---|
Adding new boards | 1 | 05:45, 25 July 2015 |
Requesting dedicated portal for OE/ Yocto | 1 | 05:18, 21 June 2014 |
Let me know how to add instructions to AudioCape page | 1 | 12:27, 16 May 2014 |
Update db | 4 | 13:02, 12 May 2014 |
Fix extension and update them. | 9 | 10:58, 12 May 2014 |
Add css code | 5 | 10:46, 12 May 2014 |
There is a bug in the pinout for the Olimex USB-Serial-Cable in the section BeagleBone_Black_Serial | 7 | 05:28, 4 May 2014 |
Requesting Implementing of functions | 3 | 05:21, 4 May 2014 |
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
Hello, I would like to work on adding some great single board computers to the site. They are Freescale i.MX6 ARM boards that run linux, etc. Please let me know if I can go ahead and start adding these or if there is a method you would like to talk me through. The boards I would like to add are listed here: http://www.freescale.com/webapp/connect/displayPartnerProfile.sp?partnerId=1-4THD-4
Best Regards.
Fantastic! If there are going to be a significant number of boards, I'd suggest linking from the MainPage with 1 image and calling it perhaps "Freescale Boards" and linking to a page called perhaps FreescaleBoards from which you could link out to the content.
You can go ahead and begin adding content, but I'll need to add the MainPage link, as that page is protected.
Does this sound good?
It would be nice if we had a portal for the Yocto Project. what do you say?
ArunKumar
You know that OE and Yocto Project both have their own wikis:
http://openembedded.org/wiki/Main_Page
https://wiki.yoctoproject.org/wiki/Main_Page
I'd be happy to include both under the elinux.org umbrella though.
Let me know how to add instructions to AudioCape page
Posted them here: http://elinux.org/CircuitCo_talk:Audio_Cape_RevB#Audio_Cape_instructions_530
It increases the performance and speed. And enables something that makes it even faster.
Well, it's not that simple. We are hosted for free by OSUOSL. They are currently in the process of retiring the db server we're using. They're looking into what version of MariaDB is on the new server that we'll be migrating to.
Can you tell me exactly what the feature is that makes the 10.0 series faster? I'm not hearing any complaints about speed.
Hi please could you install extension scribunto and please fix wikieditor because it is not showing and please update all your extension because they have the news .jsom file that Mediawiki 1.24 uses. And please download the new version from git for 1.24 because it seems JavaScript is not working on here.
I've installed Scribunto but haven't tested it yet. I've installed the Echo extension. And wikieditor works for me. Try clearing your cache before editing a page, as sometime wikieditor won't show up.
SimpleAntiSpam is already installed.
LocalizationUpdates is installed now.
You'll have to give me some time to finish upgrading the other extensions.
Cheers
Please add this code
/* Extension & Skin infobox styling */ .tpl-infobox { border: 2px solid #aaaaaa; width: 280px; /* @noflip */ clear: right; /* @noflip */ float: right; margin: 0 0 0.5em 0.5em; border-collapse: collapse; background-color: white; } .tpl-infobox td { border: 2px none #aaaaaa; padding: 0.2em 0.5em; border-bottom: 1px solid #f0f0f0 !important; } .tpl-infobox-header { background-color: #aaaaaa; color: white; text-align: left; } .tpl-infobox-header td { padding-top: 0.5em; } .ext-infobox-header img { padding: 0 0.2em 0 0.5em; } .ext-status-unstable, .ext-status-unstable td { border-color: #990000; } .ext-status-unstable .ext-infobox-header { background-color: #990000; color: #ffff00; } .ext-status-experimental, .ext-status-experimental td { border-color: #ff4500; } .ext-status-experimental .ext-infobox-header { background-color: #ff4500; } .ext-status-beta, .ext-status-beta td { border-color: #ffba01; } .ext-status-beta .ext-infobox-header { background-color: #ffba01; } .ext-status-stable, .ext-status-stable td { border-color: #32cd32; } .ext-status-stable .ext-infobox-header { background-color: #32cd32; } .ext-status-unmaintained, .ext-status-unmaintained td { border-color: #8b4513; } .ext-status-unmaintained .ext-infobox-header { background-color: #8b4513; } .ext-status-magic, .ext-status-magic td { border-color: #fe57a1; } .ext-status-magic .ext-infobox-header { color: #000; background: #FFDBEB url(//upload.wikimedia.org/wikipedia/commons/thumb/2/20/Magic_wand.svg/60px-Magic_wand.svg.png) 0 0 no-repeat; } .ext-status-magic .ext-infobox-header img { visibility: hidden; padding-right: 1em; } .skin-infobox, .skin-infobox td { border-color: #a7d7f9; } .skin-infobox-header { color: #000; background: #e2f4ff; } /* For template documentation */ .template-documentation { clear: both; margin: 1em 0 0 0; border: 1px solid #aaa; background-color: #ecfcf4; padding: 1em; }
To MediaWiki:Common.css please
There is a bug in the pinout for the Olimex USB-Serial-Cable in the section BeagleBone_Black_Serial
The pinout for the Olimex USB-Serial-Cable is wrong. The Red Wire (TX) should be connected to the Receive PIN and the Green (RX) should be connected to Transmit.They must be exchanged when connecting to the serial port
Thanks Jassuncao,
Can you give me the direct internal link to the erroneous content? I can't seem to find it. Or better yet, can you simply fix it if the page is editable.
http://elinux.org/Beagleboard:BeagleBone_Black_Serial#Olimex_3_Pin_Cable_.28PL2303.29
Unfortunately, the page is not editable.
The page should be editable once you login. It's not protected. Or just tell me what to change and I'll change it.
It is protected, tried just now.
The site seems to be using the email discussing method I recommend the implementation of IRC It is easier, faster and can get more freely than using email, or get both stay.
I mean, an independant chat for every category for example #elinux_software #elinux_hardware etc. for better management in information sorting (might find some useful infos too)
Well, there are already lots of channels dedicated to both. For example #beagle. But I believe one central channel where everyone congregates increases your chance of finding someone with knowledge about whatever it is you're interested in. This also allows others to chime in and/or just follow specific chats to learn. There's also many mailing lists out there as well as bugs.elinux.org.
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |