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 |
---|---|---|
Trying to trigger a notification email | 0 | 10:10, 11 September 2020 |
eLinux account creation error | 3 | 18:14, 2 September 2020 |
Emoji In Page Title has Broken Recent Changes Tab | 1 | 12:16, 17 October 2019 |
USB 3.0 webcams known to be working | 13 | 00:04, 7 March 2018 |
Update of the RPi-section | 1 | 15:17, 4 March 2018 |
Request to promote ARTIK and ESPresso board wikis to main page 'Hardware Pages' | 6 | 12:31, 5 August 2016 |
Adding a new board. | 3 | 11:10, 5 August 2016 |
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 |
My colleague want to make eLinux account, but they got error message from eLinux now. "Error sending mail: Failed to sender:wmat@elinux.org [SMTP: Invalid response code received from server (code: 530, response: 5.7.0 Must issue a STARTTLS command first)]" Could you tell me how to solve this issue? Also, when I made eLinux account at 2020/Aug./19th, I didn't get some error message. Best Regards,
I had created a wiki article for our group's project, and the title contained an emoji. However now, any page that would load the title of the new page, including the recent changes tab cause the page to return an internal error. I don't want to cause the users of this site the inability to view that tab, so if you could delete that page it would be ok.
elinux org/Jetson_TX1 - we need to add "USB 3.0 webcams known to be working" like this (elinux org/Jetson/Cameras). how is it possible to do that. Admin please create the section "USB 3.0 webcams known to be working" in TX1 page.
Are you not able to Edit that elinux.org/Jetson_TX1 page? I see you have edited it in the past?
yes i can able to edit the existing section(contents). But i need to create the new section like "USB 3.0 webcams known to be working". if possible please create the new section.
Hi,
i registered to add my own humble RPi-Tutorials, but as i browsed through the hub and the tuts......
Is it desireable to Update the whole section (test links, build categories,...)?
Best regards, Sebastian
Hello Wmat,
Would you have a look at the new board wikis for:
...and if you find them good enough, please link them into the main Elinux wiki page under the section 'Hardware Pages'? Thank you.
Ah. I should have thought of that, sorry. I'll get a couple small pictures ready in five minutes.
Icon files are online.
ARTIK board gets the icon
ESPresso board gets the icon
I think the quality is okay, and I made the backgrounds transparent to match what's online. Thanks again.
Hello, I would like to add Qualcomm Snapdragon based open boards from Inforce that run Linux. Please let me know if I can do this myself or if this has to be done by you. The board that is relevant and needs to be added is at http://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-410-inforce-6309-micro-sbc
Cheers.
You can add 99% of the content, but I'll need to add a link from the frontpage if you require it.
I added the board to the MainPage with a link to a new page, but let me know if you name the new page differently.
I see you never did add any content to the wiki regarding your board: http://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-410-inforce-6309-micro-sbc
I don't want to put external links directly on the front page. If you'd like to add a new page, for example call it InforceSnapdragon and add content, I can add the link to it on the front page.
For now, I'm commenting out that board in the hardware section.
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?
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
Please add
/* Infobox template style */ .infobox { border: 1px solid #aaa; background-color: #f9f9f9; color: black; /* @noflip */ margin: 0.5em 0 0.5em 1em; padding: 0.2em; /* @noflip */ float: right; /* @noflip */ clear: right; /* @noflip */ text-align: left; font-size: 88%; line-height: 1.5em; } .infobox caption { font-size: 125%; font-weight: bold; } .infobox td, .infobox th { vertical-align: top; } .infobox.bordered { border-collapse: collapse; } .infobox.bordered td, .infobox.bordered th { border: 1px solid #aaa; } .infobox.bordered .borderless td, .infobox.bordered .borderless th { border: 0; } .infobox.sisterproject { width: 20em; font-size: 90%; } .infobox.standard-talk { border: 1px solid #c0c090; background-color: #f8eaba; } .infobox.standard-talk.bordered td, .infobox.standard-talk.bordered th { border: 1px solid #c0c090; } /* styles for bordered infobox with merged rows */ .infobox.bordered .mergedtoprow td, .infobox.bordered .mergedtoprow th { border: 0; border-top: 1px solid #aaa; /* @noflip */ border-right: 1px solid #aaa; } .infobox.bordered .mergedrow td, .infobox.bordered .mergedrow th { border: 0; /* @noflip */ border-right: 1px solid #aaa; } /* Styles for geography infoboxes, eg countries, country subdivisions, cities, etc. */ .infobox.geography { border-collapse: collapse; line-height: 1.2em; font-size: 90%; } .infobox.geography td, .infobox.geography th { border-top: 1px solid #aaa; padding: 0.4em 0.6em 0.4em 0.6em; } .infobox.geography .mergedtoprow td, .infobox.geography .mergedtoprow th { border-top: 1px solid #aaa; padding: 0.4em 0.6em 0.2em 0.6em; } .infobox.geography .mergedrow td, .infobox.geography .mergedrow th { border: 0; padding: 0 0.6em 0.2em 0.6em; } .infobox.geography .mergedbottomrow td, .infobox.geography .mergedbottomrow th { border-top: 0; border-bottom: 1px solid #aaa; padding: 0 0.6em 0.4em 0.6em; } .infobox.geography .maptable td, .infobox.geography .maptable th { border: 0; padding: 0; } /* Messagebox templates */ .messagebox { border: 1px solid #aaa; background-color: #f9f9f9; width: 80%; margin: 0 auto 1em auto; padding: .2em; } .messagebox.merge { border: 1px solid #c0b8cc; background-color: #f0e5ff; text-align: center; } .messagebox.cleanup { border: 1px solid #9f9fff; background-color: #efefff; text-align: center; } .messagebox.standard-talk { border: 1px solid #c0c090; background-color: #f8eaba; margin: 4px auto; } /* For old WikiProject banners inside banner shells. */ .mbox-inside .standard-talk, .messagebox.nested-talk { border: 1px solid #c0c090; background-color: #f8eaba; width: 100%; margin: 2px 0; padding: 2px; } .messagebox.small { width: 238px; font-size: 85%; /* @noflip */ float: right; clear: both; /* @noflip */ margin: 0 0 1em 1em; line-height: 1.25em; } .messagebox.small-talk { width: 238px; font-size: 85%; /* @noflip */ float: right; clear: both; /* @noflip */ margin: 0 0 1em 1em; line-height: 1.25em; background: #F8EABA; } /* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */ th.mbox-text, td.mbox-text { /* The message body cell(s) */ border: none; /* @noflip */ padding: 0.25em 0.9em; /* 0.9em left/right */ width: 100%; /* Make all mboxes the same width regardless of text length */ } td.mbox-image { /* The left image cell */ border: none; /* @noflip */ padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */ text-align: center; } td.mbox-imageright { /* The right image cell */ border: none; /* @noflip */ padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */ text-align: center; } td.mbox-empty-cell { /* An empty narrow cell */ border: none; padding: 0; width: 1px; } /* Article message box styles */ table.ambox { margin: 0 10%; /* 10% = Will not overlap with other elements */ border: 1px solid #aaa; /* @noflip */ border-left: 10px solid #1e90ff; /* Default "notice" blue */ background: #fbfbfb; } table.ambox + table.ambox { /* Single border between stacked boxes. */ margin-top: -1px; } .ambox th.mbox-text, .ambox td.mbox-text { /* The message body cell(s) */ padding: 0.25em 0.5em; /* 0.5em left/right */ } .ambox td.mbox-image { /* The left image cell */ /* @noflip */ padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */ } .ambox td.mbox-imageright { /* The right image cell */ /* @noflip */ padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */ } table.ambox-notice { /* @noflip */ border-left: 10px solid #1e90ff; /* Blue */ } table.ambox-speedy { /* @noflip */ border-left: 10px solid #b22222; /* Red */ background: #fee; /* Pink */ } table.ambox-delete { /* @noflip */ border-left: 10px solid #b22222; /* Red */ } table.ambox-content { /* @noflip */ border-left: 10px solid #f28500; /* Orange */ } table.ambox-style { /* @noflip */ border-left: 10px solid #f4c430; /* Yellow */ } table.ambox-move { /* @noflip */ border-left: 10px solid #9932cc; /* Purple */ } table.ambox-protection { /* @noflip */ border-left: 10px solid #bba; /* Gray-gold */ } /* Image message box styles */ table.imbox { margin: 4px 10%; border-collapse: collapse; border: 3px solid #1e90ff; /* Default "notice" blue */ background: #fbfbfb; } .imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */ margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */ display: block; /* Fix for webkit to force 100% width. */ } .mbox-inside .imbox { /* For imboxes inside other templates. */ margin: 4px; } table.imbox-notice { border: 3px solid #1e90ff; /* Blue */ } table.imbox-speedy { border: 3px solid #b22222; /* Red */ background: #fee; /* Pink */ } table.imbox-delete { border: 3px solid #b22222; /* Red */ } table.imbox-content { border: 3px solid #f28500; /* Orange */ } table.imbox-style { border: 3px solid #f4c430; /* Yellow */ } table.imbox-move { border: 3px solid #9932cc; /* Purple */ } table.imbox-protection { border: 3px solid #bba; /* Gray-gold */ } table.imbox-license { border: 3px solid #88a; /* Dark gray */ background: #f7f8ff; /* Light gray */ } table.imbox-featured { border: 3px solid #cba135; /* Brown-gold */ } /* Category message box styles */ table.cmbox { margin: 3px 10%; border-collapse: collapse; border: 1px solid #aaa; background: #DFE8FF; /* Default "notice" blue */ } table.cmbox-notice { background: #D8E8FF; /* Blue */ } table.cmbox-speedy { margin-top: 4px; margin-bottom: 4px; border: 4px solid #b22222; /* Red */ background: #FFDBDB; /* Pink */ } table.cmbox-delete { background: #FFDBDB; /* Red */ } table.cmbox-content { background: #FFE7CE; /* Orange */ } table.cmbox-style { background: #FFF9DB; /* Yellow */ } table.cmbox-move { background: #E4D8FF; /* Purple */ } table.cmbox-protection { background: #EFEFE1; /* Gray-gold */ } /* Other pages message box styles */ table.ombox { margin: 4px 10%; border-collapse: collapse; border: 1px solid #aaa; /* Default "notice" gray */ background: #f9f9f9; } table.ombox-notice { border: 1px solid #aaa; /* Gray */ } table.ombox-speedy { border: 2px solid #b22222; /* Red */ background: #fee; /* Pink */ } table.ombox-delete { border: 2px solid #b22222; /* Red */ } table.ombox-content { border: 1px solid #f28500; /* Orange */ } table.ombox-style { border: 1px solid #f4c430; /* Yellow */ } table.ombox-move { border: 1px solid #9932cc; /* Purple */ } table.ombox-protection { border: 2px solid #bba; /* Gray-gold */ } /* Talk page message box styles */ table.tmbox { margin: 4px 10%; border-collapse: collapse; border: 1px solid #c0c090; /* Default "notice" gray-brown */ background: #f8eaba; } .mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */ margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */ width: 100%; /* For Safari and Opera */ } .mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */ line-height: 1.5em; /* also "nested", so reset styles that are */ font-size: 100%; /* set in "mbox-small" above. */ } table.tmbox-speedy { border: 2px solid #b22222; /* Red */ background: #fee; /* Pink */ } table.tmbox-delete { border: 2px solid #b22222; /* Red */ } table.tmbox-content { border: 2px solid #f28500; /* Orange */ } table.tmbox-style { border: 2px solid #f4c430; /* Yellow */ } table.tmbox-move { border: 2px solid #9932cc; /* Purple */ } table.tmbox-protection, table.tmbox-notice { border: 1px solid #c0c090; /* Gray-brown */ } /* Disambig and set index box styles */ table.dmbox { clear: both; margin: 0.9em 1em; border-top: 1px solid #ccc; border-bottom: 1px solid #ccc; background: transparent; } /* Footer and header message box styles */ table.fmbox { clear: both; margin: 0.2em 0; width: 100%; border: 1px solid #aaa; background: #f9f9f9; /* Default "system" gray */ } table.fmbox-system { background: #f9f9f9; } table.fmbox-warning { border: 1px solid #bb7070; /* Dark pink */ background: #ffdbdb; /* Pink */ } table.fmbox-editnotice { background: transparent; } /* Div based "warning" style fmbox messages. */ div.mw-warning-with-logexcerpt, div.mw-lag-warn-high, div.mw-cascadeprotectedwarning, div#mw-protect-cascadeon { clear: both; margin: 0.2em 0; border: 1px solid #bb7070; background: #ffdbdb; padding: 0.25em 0.9em; } /* Div based "system" style fmbox messages. Used in [[MediaWiki:Readonly lag]]. */ div.mw-lag-warn-normal, div.fmbox-system { clear: both; margin: 0.2em 0; border: 1px solid #aaa; background: #f9f9f9; padding: 0.25em 0.9em; } /* These mbox-small classes must be placed after all other ambox/tmbox/ombox etc classes. "body.mediawiki" is so they override "table.ambox + table.ambox" above. */ body.mediawiki table.mbox-small { /* For the "small=yes" option. */ /* @noflip */ clear: right; /* @noflip */ float: right; /* @noflip */ margin: 4px 0 4px 1em; width: 238px; font-size: 88%; line-height: 1.25em; } body.mediawiki table.mbox-small-left { /* For the "small=left" option. */ /* @noflip */ margin: 4px 1em 4px 0; width: 238px; border-collapse: collapse; font-size: 88%; line-height: 1.25em; } /* Style for compact ambox */ /* Hide the images */ .compact-ambox table .mbox-image, .compact-ambox table .mbox-imageright, .compact-ambox table .mbox-empty-cell { display: none; } /* Remove borders, backgrounds, padding, etc. */ .compact-ambox table.ambox { border: none; border-collapse: collapse; background: transparent; margin: 0 0 0 1.6em !important; padding: 0 !important; width: auto; display: block; } body.mediawiki .compact-ambox table.mbox-small-left { font-size: 100%; width: auto; margin: 0; } /* Style the text cell as a list item and remove its padding */ .compact-ambox table .mbox-text { padding: 0 !important; margin: 0 !important; } .compact-ambox table .mbox-text-span { display: list-item; line-height: 1.5em; list-style-type: square; list-style-image: url(//bits.wikimedia.org/skins/common/images/bullet.gif); } .skin-vector .compact-ambox table .mbox-text-span { list-style-type: circle; list-style-image: url(//bits.wikimedia.org/skins/vector/images/bullet-icon.png) } /* Allow for hiding text in compact form */ .compact-ambox .hide-when-compact { display: none; }
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.