Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
43 user(s) are online (31 user(s) are browsing Forums)

Members: 0
Guests: 43

more...

Headlines

Forum Index


Board index » All Posts (billt)




Re: First user's report of new Intel HD Audio (Azalia) driver by geennaam
Just popping in
Just popping in


Maybe a weird question... Has anyone tried this driver with Qemu-sam460 emulation?

Go to top


Re: Stack USB 3.0 for OS4 at Pianeta Amiga 2012
Just popping in
Just popping in


@graff

Does the stack itself have enough in it now, that someone can make a working host controller driver, and then hub or device drivers for USB3 Superspeed? Or is current USB Stack not yet sufficient/complete to do 3.0 Superspeed drivers?

Also, any chance that those who can, have been looking at adding USB 3.1/3.2 or even 4 speeds into the stack since the last SDK udpate in 2015?

Go to top


Re: Stack USB 3.0 for OS4 at Pianeta Amiga 2012
Just popping in
Just popping in


I don't remember ever hearing anything about that. The OS4 SDK has a few clues, but are inconsistent in ways.

Documentation/AutoDocs/usbsys.doc: USB_SPEED_SUPER for a SuperSpeed Function (4800 Mb/s).


But in the Documentation/AutoDocs/usbhcd.doc file (Host Controller stuff), the USB_SPEED_SUPER is left out:

USBA_DeviceSpeed (ULONG)
This tag is used for specifying the speed of the
USB Function to add. This defines how the
hardware driver should actually be communicating
with the Function.
ti_Data is a ULONG holding a speed indicator:
USB_SPEED_LOW for a LowSpeed Function (1.5 Mb/s).
USB_SPEED_FULL for a FullSpeed Function (12 Mb/s).
USB_SPEED_HIGH for a HighSpeed Function (480 Mb/s).

If not specified the HCD *must* default to
USB_SPEED_LOW for the added Function.
If specified, but an unknown value is supplied, the
attachment must be failed. In this case
USBERR_UNSUPPORTED should be returned in the
USBA_ErrorCode tag if supplied and supported.

...

USBA_DeviceSpeed (ULONG *)
The HCD must store the speed of the USB controller in the ULONG
pointed to by ti_Data. The speed is specified using one of the
USB_SPEED_xxx constants from usb/system.h.
Since USBA_DeviceSpeed usage was not added until v2 of the USB
stack, the USB stack will fall back to expect USB_SPEED_FULL speed
(i.e. 12MBit/s) for the HCD if it does not respond to this tag.
USB2+ capable HCDs are required to support this tag, or they will
only see USB1 device attachments.


In Include/include_h/usb/system.h it DOES define the USB_SPEED_SUPER value. So, maybe USB3 is supported, or perhaps it was never completed. Has any PCIe card ever actually been announced as working and supported? I never saw anything after that 2012 thing either... :/


/* For supplying USB Device speed to USB(HC)AddFunctionA()
ti_Data is a USB_SPEED_xxx value.
If not specified the default speed used *must* be USB_SPEED_LOW.
Also used for querying HCD root bus speed using USBHCGetAttrsA() */
#define USBA_DeviceSpeed (TAG_USER+4)

#define USB_SPEED_LOW (0L) /* 1.5 Mbit/s */
#define USB_SPEED_FULL (1L) /* 12 Mbit/s */
#define USB_SPEED_HIGH (2L) /* 480 Mbit/s */
#define USB_SPEED_SUPER (3L) /* 4800 Mbit/s */



Go to top


Re: python3.8 AmigaOS4 in development
Just popping in
Just popping in


@NinjaCyborg

I'd really like to see a modern native wxWidgets port. I think there was an old 2.6 version, but I'm not sure how complete it was. There is something for it in AmiCygnix as well, but then we go through X11. wxPython would be cool.

Go to top


Re: Font dowloader does not work in Odessey
Just popping in
Just popping in


I am having this problem, having dug out my XE and tryin gto get it back to life again. It was running 4.1u6, I have installed 4.1fe and the u1, u2 and u2hf updates, so should be all up to date. Odyssey was giving me this font problem, and partial solution from Kas1e got me a little further:

@kas1e
Script use wget to download stuff, so add --no-check-certificate parametr to wget. To that big string of mess, add it right after that Datas/wget --tries 10 (don't forget to put spaces before and after, so it will be as normal parametr)


But... While some fonts were downloaded this way, it failed and complains when it gets to georgi32, and says OWB WON'T work in the requestor. Same as for the first font, andale32, and also from sourceforge, so not sure what happened for this one after several worked fine.

Can we get the fonts manually and install separately, for Odyssey to use?

I have never used odyssey before, but the AmiStore setup recommends Odyssey. I haven't figured out how to use AmiStore yet, clicking buy and add to cart but nothing happens but more login requestors from it, so hopefully this browser bit will help something functional to happen for AmiStore...

Go to top


Re: pci-e/m.2 ssd on x5000?
Just popping in
Just popping in


@walkero

Per the subject, I take it as asking if the PCIe based NVME style (no SATA at all) ssd cards in m.2 slot.

For booting, that would likely require uboot support.

For other than booting, and after booting, that would require OS driver.

I know not of either, but do hope that NVME drivers do happen (or already did), and uboot support for booting them too.


Go to top


Re: Warp3D Nova Tutorials Book Released
Just popping in
Just popping in


@Capehill

Quote:
GPU temperature might be useful to diagnose potential issues.


And also for performance monitoring/throttling and power management.

Go to top


Re: Maximum memory X1000
Just popping in
Just popping in


The cpu can do 16GB on each of rhe two memory controllers. Too bad we can only do 8, or was the user guide for x1000 written before larger modules came to be? 4x4GB could give us 16GB, and 4x8GB could give us 32GB, if the slots are wired to support that. Yea, silly if we can only use 2GB of that, but curious...

Go to top


Re: Maximum memory X1000
Just popping in
Just popping in


What is the max memory the hardware is capable of? Does Linux or any OS support that?

Go to top


Finally learning Java using Jamiga
Just popping in
Just popping in


So I finally have reason to learn Java. I struggled to get Jamiga running and figure out how to use it, but was able to compile and run a hello world program, and hope to use Jamiga as my learning platform for the language.

It seems that it's been a while, does progress continue in the background, or was it too much to keep interest in?

Go to top


Re: X1000 CPU cooling
Just popping in
Just popping in


I also would like to know the CPU heatsink style. After finally coming across the rarely for sale x1000, and needing to repair damage caused by shipping company, I'd like to get a nice big cold heatsink kit.

It seems the magmabreath and magmacolluseum I had on my list for a long time have ceased to exist.

Any suggestions?

Go to top


Re: New cygwin cross-compiler tests
Just popping in
Just popping in


@kas1e

Is there a mirror of the utility base article linked to? That is a dead link in the copy of zero hero's page...

Go to top


Re: Contact person?
Just popping in
Just popping in


@jaokim

I'd been interested in taking over at o e point, but have not had opportunity to investigate making that happen (legal entity options, responsible si ilities, how to do it right and not get in trouble etc) I'd been involved, and will try to pass on a message if you like. Pm me with details.

Go to top


Re: Timberwolf is now open source
Just popping in
Just popping in


@tfrieden

Thank you Thomas and Hans-Joerg!


Go to top


Re: Any altivec experts? (H.264 codec)
Just popping in
Just popping in


@Raziel

Quote:
btw, you don't need to get hardware for AmigaOS4.1 (at least you are not forced to).
As soon as AmigaOS4.1 FE becomes available you can set up a working installation with your favourite UAE emulator


Qemu does not emulate altivec, thus *UAE does not emulate altivec.

Unless someone adds that capability to Qemu...

After saying that I do see Altivec patch messages, but I said it based on TODOs showing up in Altivec instructions group in the source tarball.


in Qemu 2.1.50 file ./target-ppc/STATUS there are a lot of
Quote:
INSN KO Altivec missing


And this is also the case after updating to 2.1.91


Edited by billt on 2014/11/15 2:31:09
Edited by billt on 2014/11/15 2:58:38
Edited by billt on 2014/11/15 3:01:54
Go to top


Re: Any altivec experts? (H.264 codec)
Just popping in
Just popping in


@tlosm
Quote:
i dont know how much important will have altivec optimized decoder , hope it in case will help only x1000


A1XE G4 has altivec as well, X1000 is not alone with that. Also very much hoping for the PPC Lpatop to become real, which claims to target 64bit and altivec enabled CPU, though that does seem a bit early to call real just yet. From what they have said so far, it matches closely with how I'd make an Amiga laptop, so I at least think they are on a realistic path, if they continue the journey to the end of that path...

http://www.powerpc-notebook.org/

I would not choose to make a PPC board for Amiga users without Altivec at this point, and I don't understand why others do. (I suppose it's related to demand from other markets, familiarity with 4xx or other particular chips by the hardware designers, maybe cost but I would consider that less important than other things)

If Qemu had altivec, then WinUAE-PPC would have it too, and perhaps that's a reason to add it. Or adding Articia+686b to Qemu proper would be a better reason to add altivec to Qemu...

Go to top


Re: OS3.9 filesystems question
Just popping in
Just popping in


OK, here's where I am with this. I've lost my WORK partition. I didn't have anything on it yet, so not a big loss, but I've been unable to get it back up at the beginning again.

I have OS4.1 Classic on as SFS00 partition. That part still works when I remove the WORK hardfile in WinUAE.

Adding WORK as an SFS02 partition gives me this error message from AmigaDOS at boot time (I do not get to Workbench anymore):

Amiga ROM Operating System and Libraries
Copyright (C) 1985-1993 Commodore-Amiga, Inc.
All Rights Reserved.
*** Error: Can't allocate enough memory to load kernel
Stopped
Bootloader failed returncode 20


This work partition hardfile is 100GB. The first time I boot OS4.1 Classic with this newly created hardfile, I am able to run Media Toolbox to partition it. The next boot shows the unformatted Work: icon. I click and want to go to format, but at this point it's usually likely to crash. The enxt boot after seeing the Work: unformatted icon is the above error message. I get this even if I was nto able to get through to quickformat, so Work: is still UNformatted. I'm not sure why I am able to boot and see all this only one time, as I'm not convinced that a hung session before I am able to start a format should have changed anything from the previous, more successful boot.

I've also tried with a 10GB Work hardfile in case 100GB is for some reason too big. The hardfiles (both sys: and work: of whatever capacity) are on the CSPPC accelerator SCSI controller.

Any idea what this error means, and how to resolve it?

SFS filesystem is of course in the RDB for the sys: drive, for bot SFS/00 and SFS/02, and sys: is SFS/00 format.

I just realize I've said "partition" a lot. Work: and SYS: are on separate hardfile drives. This lets me keep my workign SYS: drive with OS4.1 upd6+ while I experiment with work: stuff.

In WinUAE I greated 100000MB hardfile, for SFS/00 I select SFS in the filesystem choices, for SFS/02 I select custom and give it 0x53465302, then click create and give it filename. Then click Enable RDB Mode. Then boot up, and use Media Toolbox to install, where I click read configuration then accept and save to disk, then go to partition, giev it full capacity for single partition named work:, not bootable, select SFS/00 or SFS/02 and change Blocksize to 512, then OK, OK, Save to Disk, Yes Save buttons and quit Media Toolbox, then successfully reboot one time when I can see the unformatted Work partition icon, which will most likely crash/hang, and then any reboot after that gives the above error message.

Now, there have also been a few times that I was able to do a QuickFormat instead of hang/crash. When I get this far, it does appear to work, and I can access the drive during this same boot. But again, next boot, I get the error message above.

OK, I just noticed that for my OS4.1 SYS: partition I did have SFS/00 filesystem set up in the RDB, but not SFS/02. In OS3.9 SYS: I DID have both SFS/00 and SFS/02 set up. I added this for SFS/02 as well, so both are in RDB via MediaToolBox, but same thing. I can install/partition, reboot one time, successfully QuickFormat, copy files onto this newly formatted drive/partition, reboot again and get the error above.


OK, now for OS3.9 side of this. I installed the newest SFS filesystem that you all had linked me to previously, and set both SFS/00 and SFS/02 to that filesystem in the RDB using HDtoolbox. When Work drive is connected, I get an endless yellow "recoverable" GURU, but nothing else. With Work drive disconnected, then OS3.9 boots up fine. I do not at the moment remember if I have applied any BoingBag updates to this OS3.9 install. Is there an easy way to tell this? Would this be important?

I will also try to get the OS4.1 Classic SFS filesystem out and try to install it in OS3.9 L and RDB to see if that will help with the Yellow GURUs. OK, I've just done that, and still get the Yellow GURU in OS3.9. Error 0100_000c Task 00031fe8.Clicking left mouse to continue takes me right back to the same Yellow error GURU in an infinite loop.


In all cases of both OS4.1 Classic and OS3.9 errors, if I remove this Work drive then I can boot just fine.

So, is there a problem with using SFS/02?

My OS4.1 SYS: is SFS/00 so that is OK, and OS3.9 SYS: is FFS/International format.

Go to top


OS3.9 and OS4.1 (Classic) filesystems question
Just popping in
Just popping in


Hi All,

I'd like to set up a work drive/partition that uses best filesystem that is also available in OS4.1 Classic, to get me the biggest, fastest partition possible, or at least reasonable.

This is for use in WinUAE, using hardfiles.

I've set up an initial test Work partition in OS4.1 Classic using SFS/02 filesystem. 100GB drive, one partition filling the whole thing.

Now, I'd like to be able to access it in my OS3.9 emulation as well, and take this hardfile back and forth between the two emulation configs. It seems like SFS is supposed to be available in OS3.9, but I'm having trouble finding it, at least the SFS/02 version. So perhaps I need to step back and use SFS/00 instead, and use the SFS 1.277 on aminet. Perhaps that is SFS/02 capable (for files > 4GB in case I ever need to do that, though not sure I will), but just isn't obvious to be so.

So, does anyone have suggestions for this sort of thing? Does the Aminet SFS kit support my OS4.1 drive? Do I need something different? Would a different filesystem be better? (I don't need to boot Work:)

As I've finally just found my pack of Amiga CDROMs, I've just installed OS3.9, and have yet to get to any boingbags, though I have found and downloaded those now, in case I need to do those first.



Edited by billt on 2014/10/3 16:59:41
Go to top


Re: Is GCC totally bugged, or am I just going crazy?
Just popping in
Just popping in


@ChrisH

Quote:
There is NO timing sensitive code (it's single-threaded & only makes a few DOS calls)... But even if it WERE timing sensitive, how does a printf() which is (intentionally) never executed caused a timing problem?!?


You mentioned there are no optimizations on.

You've added an if block. That's new, so let's for the moment set the printf aside, and focus on the if itself. The if condition check may be accomplishing the same mysterious magic that the printf did before you wrapped it in an always-false if block.

If you remove both the new aways-false ifblock and hte printf inside, does your code continue to work, or does it revert to failure as it did before adding printf and if checks? If it goes back to failure, then that if is causing something different to happen.

What could an if block cause to happen, particularly an always-false one that will never run its contents? Well, the a==b check is done. If nothing else, that takes time, moved the PC, maybe did a memory access and changed the pipeline state compared to the program without this a==b check.

If you can replace the if and its printf contents with an empty while loop of an iteration or two, and things will still work, but the program fails without anything in that location, then somehow it's timing related.

Go to top


Re: Is GCC totally bugged, or am I just going crazy?
Just popping in
Just popping in


@ChrisH

Without knowing what you're trying to do, I've seen that sort of behavior in timing sensitive bits of code before. The printf, or an if condition check, slowed things down just enough to work. Or in other cases took too long, and interfered with what we wanted. This was in DMA type stuff, when we were waiting for something from the controller. If we waited too long, then the buffer overflowed in the meantime and we lost data. If things didn't take long enough, then we tried to read a buffer that wasn't full yet, and we missed some data not there yet. So we had to figure out what the right thing was to wait on, and where we could and could not put printfs for debugging output.

Go to top



TopTop
(1) 2 3 4 ... 11 »




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project