sam
Administrator
MOTM October '18
i'll follow you wherever you lead
Join Date: Mar 11, 2015 22:19:26 GMT
Posts: 3,891
Likes: 7,233
Location: United Kingdom
Last Online: Aug 19, 2017 18:26:59 GMT
|
Post by sam on Feb 22, 2017 0:11:48 GMT
different linux distros can't even share drivers (having the same kernel)? progressive. Ubuntu has typically had better driver support than the other distros as it's the "mainstream" distro. It is annoying why they can't share the drivers, but I think it's just because of licensing issues.
|
|
⋆niki⋆
Member
MOTM March '17; MOTM March '18
i've seen your best side, you got to see my worst; it's not the first time but this one really hurts
Join Date: Jul 1, 2015 11:13:36 GMT
Posts: 2,967
Likes: 3,725
Location: Hungary
Last Online: Dec 18, 2023 0:11:47 GMT
|
Post by ⋆niki⋆ on Feb 22, 2017 7:27:58 GMT
So I tried to fix this problem on my website - Avril's insta is not visible there anymore. It says it's private. I have this problem for awhile. What's wrong?
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Feb 23, 2017 8:29:03 GMT
So I tried to fix this problem on my website - Avril's insta is not visible there anymore. It says it's private. I have this problem for awhile. What's wrong? Uhm, sorry don't know much about HTML. Maybe try another instagram widget? 😉
|
|
⋆niki⋆
Member
MOTM March '17; MOTM March '18
i've seen your best side, you got to see my worst; it's not the first time but this one really hurts
Join Date: Jul 1, 2015 11:13:36 GMT
Posts: 2,967
Likes: 3,725
Location: Hungary
Last Online: Dec 18, 2023 0:11:47 GMT
|
Post by ⋆niki⋆ on Feb 23, 2017 8:32:25 GMT
So I tried to fix this problem on my website - Avril's insta is not visible there anymore. It says it's private. I have this problem for awhile. What's wrong? Uhm, sorry don't know much about HTML. Maybe try another instagram widget? 😉 We have a tumblr site. IDK how it is working there. I only know my design staff (that one girl) can't find a solution:D
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Feb 25, 2017 7:19:11 GMT
Uhm, sorry don't know much about HTML. Maybe try another instagram widget? 😉 We have a tumblr site. IDK how it is working there. I only know my design staff (that one girl) can't find a solution:D I'm lost, I don't use tumblr sorry maybe ask sam ?
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Feb 25, 2017 7:20:39 GMT
Intel
|
|
332
Member
Banned
Join Date: Sept 22, 2016 23:46:35 GMT
Posts: 176
Likes: 39
Last Online: Apr 2, 2017 19:03:47 GMT
|
Post by 332 on Feb 25, 2017 17:21:46 GMT
Uhm, sorry don't know much about HTML. Maybe try another instagram widget? 😉 We have a tumblr site. IDK how it is working there. I only know my design staff (that one girl) can't find a solution:D whats the problem might be able to help
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Feb 28, 2017 22:24:08 GMT
In my spare time, I am trying to write an OS (duh), but this is not going to be "extremely soon" of course. And it's in such a rudimentary state yet. Neverthless, it's a very serious occupation, I've got the idea of doing this so long time ago. Moreover I even try to turn it into my work. have no idea how yet, but now i am writing a firmware part of the project, guess at some points it might drive me into having this as a job, not just "hobby". What I wanted to say here, it should be somehow related to this place, I am thinking on letting (assigning) some component of the OS Avril's name. Would be extremely embarrassing and cool simultaneously. The OS name is kind of defined (long time ago), but this is a huge thing, there is a lot of things to get such a respectable name on them. For example, my OS is going to have Environment Subsystems - API sets and supporting processes, alowing programs written using those APIs to run. This is a Windows NT concept, no wonder, my OS will be NT-like. NT intially had Win32 subsystem, Posix subsystem, OS/2 subsystem. The former won and the latter two were discarded long time ago. Win32 (WinAPI) is actually that behemoth upon which everything in the Windows world is built. And this is ~93% of world's desktop computers. So, subsystems. They are very important. My OS is going to have a "Default" subsystem, which is permanent, always present and everything else can rely on its presence. This will be, at least at first, a basic subset in spirit of WinAPI, whithout graphics though (without many things in fact), graphics is hard, too hard. And the second is Posix subsystem, this one is for bringing into my OS those myriads of applications written for it - they are free and that is their main advantage. Again without graphics. In fact, Posix doesn't cover graphics. I won't pretend I am able to implement a full set of APIs to run Windows applications, that is not my goal, not to mention pulling Windows apps off into another execution environment sounds as something not exactly legal. But the main thing it's too hard to supply a full WinAPI set and everything following needed for running Windows applications. Writing every application for my own API by myself is the extremity of complexity. Unfeasible at all. So porting freely available programs (free at the source code level, by the license, being yet more precise), - is the way of attracting users and letting the project to be something more than just a hobby interesting to only myself. Thus Posix, because there is a lot of its implementations. I am looking at the BSD space, I just don't like GPL. But the linux application binaries' compatibilty layer atop of the POSIX subsystem would be a good goal too. For the far future. It might be a Subsystem Extension. Default subsystem, being the most native one, apart from the possibility of having programs entirely written for it (system utilities for example) as well might serve as a means of improvements for ports of applications from other Subsystems, I mean a POSIX program could take advantage of the features of the Default Subsystem not available in Posix. Or use it for performance reasons. Basically Subsystems are the doors for user programs to the capablities their hardware and OS have. But "Default" Subsystem sounds a bit formal. Calling it WinAPI hardly is a good idea, because it's ambiguous and confusing, and possibly illegal. So maybe Avril? - What requirements for your program package are? - This program is written for Avril. Or better yet: - This program is written to run on Avril. There are even more funny phrases with this. I am not sure it's the best fit for Avril name there yet, but I definitely want to include it into my work. Of course this is not a 1:1 wax statue of her or endless cute paintings of her, she hardly could appreciate it, still it's important for me to do so. Because everyone stays a kid forever at least to some degree. I just wrote this because I am on a very exciting point of the project - preparing to the first runs on a bare metal! Bitches! This intensifies thinking about it even more than I do ordinarily and the wish to talk about it. But the topic is too specific. Before I get banned at all for non-compliance, wanted to share this.
|
|
332
Member
Banned
Join Date: Sept 22, 2016 23:46:35 GMT
Posts: 176
Likes: 39
Last Online: Apr 2, 2017 19:03:47 GMT
|
Post by 332 on Mar 1, 2017 0:25:18 GMT
z4v4l i am one that is interested in the progress of this project. would you use shell to call a program to boot up? or power shell CMD type shell to call a program to boot up? i do realize they are the same with differences
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Mar 1, 2017 13:09:36 GMT
z4v4l i am one that is interested in the progress of this project. would you use shell to call a program to boot up? or power shell CMD type shell to call a program to boot up? i do realize they are the same with differences Thank you. For booting, OS will use UEFI - it's a firmware, in fact this is where I am now - writing my own UEFI.) Not at every platform I'll need this - only for ARM and MIPS. For x86, I'll need to write only an OSLoader - an UEFI application, which, using UEFI Boot Services, loads the OS. My firmware subproject is for checking is this possible for me to do it at all. Addintionally there is no much implemenation of it on ARM. And no for MIPS at all. Here (in the firmware environment), as a shell first I use a very custom and chaotic CLI - command line interface - a mix of the shell and debugger. It can't launch anything - only jerk internal parts of the FW. Later, when it is more stable and full of features, I'll port edk2 shell into it, it's a UEFI shell, very powerfull, it's a part of Tianocore project. You probably used it (as a "BIOS") if your laptop/PC is not that old. But vendors customize it heavily, adding their buggy whistles and doodles, - "to simplify things", to the different degree of ugliness, so its view and behavior are not very consistent across different computers. Don't assume UEFI shell (or wider - UEFI Boot Manager) is that asshole that doesn't let you switch something on or off on your machine. It's not its fault. Next, that above was about the firmware. OS first, again, will use sort of internal kernel shell - development environment, not more. When it comes to the user-mode applications, first of all I'll need to implement user-mode OS components - Session Manager - smss.exe, it's the very first user-mode process started, it's a big boss. It manages a lot of things - creates page files, starts Winlogon.exe process - which is in charge of logons, shutdowns etc, Services.exe - service manager, Lsass.exe - local security authentication subsystem, dealing with "dat security" for example, but as well - it launches Environment Subsystems, mentioned above. They are "personalities" for the OS. And only there begin things where the word "shell" and "running user programs" start to have sense. Depending on what subsystems were configured to start, Session Manager will chose what to launch. Only Default subsystem is always on, anything else is "on demand" if not cofigured otherwise. And here, answering your question, what shell is to be used to lauch programs - it depends on what subsystem took control over the console - if it is Posix, then launching programs (and services - "daemons" in posix parlance) is its duty. How user programs are launched there, when there is no GUI? Right - "sh" process is in charge of this. It takes over the console and provides TUI - text user interface, for the user. There, a user typing names of his/her program will launch them. What exactly shell I'll chose? I don't know yet, what is easier to port. I am thinking on bash or ksh. But since interface of the latter is embedded in the POSIX by itself, it is a favorite, I guess. But if they or even more shells would be ported, then this will be the choice of the user what shell to use. One just needs to signal this somewhere in the Registry. If no posix subsystem was launched at the init time, then Default subsystem shell will be started and take control over the console. It's planned to be something similar to the good old Windows command interpreter - CMD.EXE. Speaking about PowerShell. You mean PowerShell, this colossal thing from MS? It would be very cool to have that. But not for beginning. It's too complex, it depeneds upon .NET Framework(s), which by themselves are monstrosity by volume of the work needed to implement them. Maybe it will be ported by someone else.) But those are all plans. For now I am at the stages where all the "shell" is a custom iternal interface for debugging. There is such a driver Bootvid.sys, its role is to supply a very basic graphic support at the very start of OS booting. Windows kernel explicitly imports functions from it (at least as of XP). In my project, I initially assigned for my Bootvid.sys a little more responsibilities - it is my shell, debugger and everything else dealing with interaction with me.
|
|
332
Member
Banned
Join Date: Sept 22, 2016 23:46:35 GMT
Posts: 176
Likes: 39
Last Online: Apr 2, 2017 19:03:47 GMT
|
Post by 332 on Mar 1, 2017 22:39:35 GMT
.net yes very difficult i tried and soon found reality that i am just a wannabe then went to a programmer's forum and downloaded it from a developer there that actually knew what do. same as you know what to do.
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Mar 10, 2017 0:00:10 GMT
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Mar 10, 2017 12:52:34 GMT
^ w8n4s8n T1_Spork, tell me is there on the board (or on the package) the crossed chemical sign of lead? Something like (Pb) but with a diagonal line over it. I am a freak of eliminating lead from everywhere.
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Mar 13, 2017 13:42:45 GMT
^ Ok, didn't know that was a secret. x^D here's my board. it's the first one I am programming withing my project mentioned. It's tiny, and draws only 750-800 mA of current at maximum (stressed) usage, 210 mA idling and 30 mA suspended. And this is MIPS processor! With which I am somehow so obsessed.) In the huge sea of ARM boards this MIPS machine is just a rarity. I told about my far plans, but what's the current work is? It is a intialization steps for this board. Shortly, the steps taken and what needs to have been taken are: 1) Internal ROM code starts at power on and makes some very initial set up. Unfortunetely it's not well documented. Mostly not because of "secrets", rather - laziness. 2) It checks for what to boot next, looking at boot_sel flags. Normally it's a (bare) NAND chip where Crappux Linux and uboot reside. It configures NAND controller, reads NAND array, checks for some signatures at the beginning of the 1st NAND pages, loads uboot image and transfers control to it. You, by switching the jumper and pressing the button may direct it to boot from an SD card which slot (full sized) you are staring at just right above. We are going to not touch NAND first and our FW goes onto SD card. We put our SEC blob at the beginning of the SD card, so ROM code is able to find, load it and jump to it. 3) This where our code takes control. ROM code loads us into TCSM - tightly coupled shared memory, it's SRAM, common SDRAM is not yet initialized! TSCM is only 14KB of available space - too few for monstrous deployment like Pei phase is, so we skip it, transfering its responsibilities to the SEC which will do them very ascetic way, only very needed work, among that the first one is initializing SDRAM, and then loading our main image - Dxe phase's main module - Dxe.exe, the core of the firmware. For this we also need to read SD card. So our SEC module does: 4) configure CPU (branch predictor, caches, exception/interrupt handling configurations) 5) initilialize OS Timer - one of many timers at SoC, as its name implies it's freaking "heart" timer for OS processes (like thread dispatching/scheduling for example) 6) initialize PLL's for clock signals, there are 4 - APLL (CPU, L2 cache, AHB buses, peripherals), MPLL (SDRAM memory, peripherals), EPLL (audio mostly, don't touch it yet), VPLL (for VPU - video encoding/decoding hardware, not touching yet) 7) initialize interrupt controller, we want to use OS timer with interrupts enabled at it, not polling needlessly, we may do it, we may disable all interrupts but this one - from the OS timer. Cool. That's what we need to do here. here we might make some blinking with the LED, it can be either red or blue, a good way to encode flow of process for eye. 8) we initialize UART4 for terminal connection with our workstation, so that we may see our prints, what's going on there - very important thing. 9) and finally, we need to start DDRC and DDR PHY init. those are two parts of SDRAM management. DDR controller and DDR PHY controller. First is somehow documented the second isn't at all. So messing around uboot code is the way to get an idea what to do. Very hard and exhausting part. After all the prestidigitation with endless registers of both, having ensured SDRAM is working, we might want to run some simple test at it, making sure written and read back data are the same. If this is the case, that's almost all for the SEC phase and 10) we go prepare HOB (Hand-off block) list for the Dxe Foundation - this data describes memory map for Dxe. 11) we read SD card, our FV - firmware volume, searching for PE (Portable Executable) image for Dxe, Dxe.exe. Finding it, we load it. 12) verify its validity, checking some PE fields, calculate jump address from ImageBase and AddressOfEntryPoint fields and jumping there! That's all. The first phase has done its work. Next Dxe will deploy the UEFI environment and transfer control to BDS - boot device selection phase - UEFI Boot Manager. Here we should choose what OS to load, trying OS Loaders' UEFI applications in (specified) order (this is done with help of Boot options). But since we don't have yet a fully working environment, we will run here UEFI shell instead. Now I am dealing with PLL's.
|
|
Deleted
Deleted Member
Join Date: Mar 28, 2024 20:07:30 GMT
Posts: 0
Likes:
Last Online: Mar 28, 2024 20:07:30 GMT
|
Post by Deleted on Mar 14, 2017 21:42:40 GMT
|
|