aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| | * client: added function client_by_fd()Max Kellermann2008-09-011-13/+21
| | | | | | | | | | | | | | | The code becomes less complex and more readable when we move this linear search into a separate mini function.
| | * client: return early in client_new()Max Kellermann2008-09-011-30/+31
| | | | | | | | | | | | This saves one level of indent.
| | * client: renamed all public functionsMax Kellermann2008-09-016-19/+19
| | | | | | | | | | | | | | | | | | Functions which operate on the whole client list are prefixed with "client_manager_", and functions which handle just one client just get "client_".
| | * client: renamed internal functions and variablesMax Kellermann2008-09-011-297/+296
| | | | | | | | | | | | | | | Rename all static functions, variables and macros which have "interface" in their name to something nicer prefixed with "client_".
| | * client: renamed Interface to struct clientMax Kellermann2008-09-011-19/+19
| | | | | | | | | | | | | | | | | | | | | Second patch: rename the internal struct name. We will eventually export this type as an opaque forward-declared struct later, so we can pass a struct pointer instead of a file descriptor, which would save us an expensive linear lookup.
| | * renamed interface.c to client.cMax Kellermann2008-09-017-7/+7
| | | | | | | | | | | | | | | | | | | | | I don't believe "interface" is a good name for something like "connection by a client to MPD", let's call it "client". This is the first patch in the series which changes the name, beginning with the file name.
| | * imported list.h from the Linux kernel sourcesMax Kellermann2008-09-012-0/+485
| | | | | | | | | | | | | | | | | | | | | linux/list.h is a nice doubly linked list library - it is lightweight and powerful at the same time. It will be useful later, when we begin to allocate client structures dynamically. Import it, and strip out all the stuff which we are not going to use.
| * | Merge branch 'mk/strset' into mk/playlistEric Wong2008-09-097-151/+245
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * mk/strset: use strset.h instead of tagTracker.h strset: fix duplicate values added string set library Conflicts: src/dbUtils.c src/tagTracker.c
| * | | fix -Wcast-qual -Wwrite-strings warningsMax Kellermann2008-09-095-27/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous patch enabled these warnings. In Eric's branch, they were worked around with a generic deconst_ptr() function. There are several places where we can add "const" to pointers, and in others, libraries want non-const strings. In the latter, convert string literals to "static char[]" variables - this takes the same space, and seems safer than deconsting a string literal.
| * | | playlist: return -1 after assert(0)Max Kellermann2008-09-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | print_playlist_result() had an assert(0) at the end, in case there was an invalid result value. With NDEBUG, this resulted in a function not returning a value - add a dummy "return -1" at the end to keep gcc quiet.
| * | | command: concatenate strings at compile timeMax Kellermann2008-09-091-27/+33
| | | | | | | | | | | | | | | | | | | | | | | | String literals (including those defined in CPP macros) can be concatenated at compile time. This saves some CPU cycles in vsnprintf() at run time.
| * | | audio: don't pass "fd" to {en,dis}ableAudioDevice()Max Kellermann2008-09-093-18/+21
| | | | | | | | | | | | | | | | No protocol code in the audio output library.
| * | | volume: don't pass "fd" to changeVolumeLevel()Max Kellermann2008-09-093-21/+26
| | | | | | | | | | | | | | | | | | | | The "volume" library shouldn't talk to the client. Move error handling to command.c.
| * | | directory: printDirectoryInfo() does not call commandError()Max Kellermann2008-09-092-4/+4
| | | | | | | | | | | | | | | | Move another ocurrence of error handling over to command.c.
| * | | directory: don't pass fd to traverseAllIn()Max Kellermann2008-09-096-32/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch continues the work of the previous patch: don't pass a file descriptor at all to traverseAllIn(). Since this fd was only used to report "directory not found" errors, we can easily move that check to the caller. This is a great relief, since it removes the dependency on a client connection from a lot of enumeration functions.
| * | | directory: don't pass fd to traverseAllIn() callbacksMax Kellermann2008-09-094-51/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Database traversal should be generic, and not bound to a client connection. This is the first step: no file descriptor for the callback functions forEachSong() and forEachDir(). If a callback needs the file descriptor, it has to be passed in the void*data pointer somehow; some callbacks might need a new struct for passing more than one parameter. This might look a bit cumbersome right now, but our goal is to have a clean API.
| * | | playlist: PlaylistInfo() does not call commandError()Max Kellermann2008-09-092-6/+15
| | | | | | | | | | | | | | | | | | | | | | | | Continuing the effort of removing protocol specific calls from the core libraries: let the command.c code call commandError() based on PlaylistInfo's return value.
| * | | playlist: don't pass "fd" to storedPlaylist.c functionsMax Kellermann2008-09-096-150/+126
| | | | | | | | | | | | | | | | | | | | Return an "enum playlist_result" value instead of calling commandError() in storedPlaylist.c.
| * | | playlist: don't pass "fd" to playlist.c functionsMax Kellermann2008-09-094-185/+245
| | | | | | | | | | | | | | | | | | | | | | | | The playlist library shouldn't talk to the client if possible. Introduce the "enum playlist_result" type which the caller (i.e. command.c) may use to generate an error message.
| * | | playlist: showPlaylist() and shufflePlaylist() cannot failMax Kellermann2008-09-093-10/+8
| | | | | | | | | | | | | | | | Make them both return void.
| * | | playlist: moved "repeat" and "random" value checks to command.cMax Kellermann2008-09-093-24/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Client's input values should be validated by the command implementation, and the core libraries shouldn't talk to the client directly if possible. Thus, setPlaylistRepeatStatus() and setPlaylistRandomStatus() don't get the file descriptor, and cannot fail (return void).
| * | | playlist: fix FILE* leak in appendSongToStoredPlaylistByPath()Max Kellermann2008-09-091-0/+2
| | | | | | | | | | | | | | | | | | | | When an error occurs after the file has been opened, the function will never close the FILE object.
| * | | playlist: replaced run-time check with assertionMax Kellermann2008-09-091-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "fspath" argument of writeStoredPlaylistToPath() must never be NULL. There should be an assertion on that, instead of a run-time check. [ew: fspath => utf8path]
| * | | playlist: added is_valid_playlist_name()Max Kellermann2008-09-092-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function valid_playlist_name() checks the name, but it insists on reporting an eventual error to the client. The new function is_valid_playlist_name() is more generic: it just returns a boolean, and does not care what the caller will use it for. The old function valid_playlist_name() will be removed later.
| * | | dbUtils, playlist, directory: pass constant pointersMax Kellermann2008-09-096-37/+38
| | | | | | | | | | | | | | | | The usual bunch of const pointer conversions.
* | | | alsa: re-enable-nonblocking, but sleep if busyEric Wong2008-09-101-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of letting ALSA block for us (and potentially allowing something stupid on certain hardware or drivers), we do the sleeping ourselves. We calculate the sleep to be a fraction of period_time to avoid oversleeping (and thus audible skipping).
* | | | Merge branch 'mk/strset'Eric Wong2008-09-097-149/+255
|\ \ \ \ | | |/ / | |/| | | | | | | | | | | | | | | | | | * mk/strset: use strset.h instead of tagTracker.h strset: fix duplicate values added string set library
| * | | use strset.h instead of tagTracker.hMax Kellermann2008-09-096-173/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | With a large music database, the linear string collection in tagTracker.c becomes very slow. We implemented that in a quick'n'dirty fashion when we removed tree.c, and now we rewrite it using the fast hashed string set.
| * | | strset: fix duplicate valuesMax Kellermann2008-09-091-1/+1
| | | | | | | | | | | | | | | | | | | | Due to a minor typo, the string set had duplicate values, because strset_add() didn't check the base slot properly.
| * | | added string set libraryMax Kellermann2008-09-093-0/+195
| |/ / | | | | | | | | | | | | | | | | | | | | | "struct strset" is a hashed string set: you can add strings to this library, and it stores them as a set of unique strings. You can get the size of the set, and you can enumerate through all values. This will be used to replace the linear tagTracker library.
* / / metadata_pipe: kill "writer is ahead of reader" messageEric Wong2008-09-091-4/+1
|/ / | | | | | | | | The writer can be far ahead of the reader during HTTP stalls; so stop spamming the logs with this message.
* | alsa: use blocking instead of non-blocking writeEric Wong2008-09-081-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | The way we used non-blocking mode was HORRIBLE. It was non-blocking to ALSA, but we end up blocking in a busy loop that does absolutely NOTHING but retry. We don't check for playback cancellation (like we do in decoders) or anything. This is seriously broken and I can imagine it affects people on fast CPUs more because we do asynchronous output buffering and our ALSA device will always have data ready.
* | alsa: show more debugging informationEric Wong2008-09-081-10/+14
| | | | | | | | | | | | | | | | | | Print out {buffer,period}_{size,time}. Not sure if this is going to help. I've been searching everywhere looking for a possible clue as to what's causing the high CPU usage problems... Also, add device information to some messages I missed earlier.
* | alsa: cleanup the mmap logic a bitEric Wong2008-09-081-8/+6
| |
* | alsa: snd_pcm_sw_params_set_xfer_align is deprecatedEric Wong2008-09-081-3/+0
| | | | | | | | | | Lets not use deprecated functions. It's apparently possible to not care about the sw_params stuff at all!
* | alsa: only run snd_config_update_free_global once atexitEric Wong2008-09-071-3/+7
| | | | | | | | | | | | | | | | | | This is safer than the patch in http://www.musicpd.org/mantis/view.php?id=1542 with multiple audio outputs enabled. Sadly, I only noticed that patch/problem when I googled for "snd_config_update_free_global"
* | alsa: move bitformat reading code out of the wayEric Wong2008-09-071-16/+12
| |
* | alsa: always print the period_time we setEric Wong2008-09-071-2/+1
| |
* | alsa: avoid unnecessary heap usage if we don't set a device nameEric Wong2008-09-071-11/+12
| |
* | alsa: get rid of the needless canPause flagEric Wong2008-09-071-3/+0
| | | | | | | | | | We never use it for anything anyways as we release the device entirely on pause.
* | alsa: avoid reassigning ad->writeiEric Wong2008-09-071-7/+4
| | | | | | | | This saves me precious terminal space
* | alsa: add reasoning for the non-portable macroEric Wong2008-09-071-0/+2
| |
* | alsa: capitalize "ALSA" consistently in messagesEric Wong2008-09-071-16/+9
| | | | | | | | That's the name of this project.
* | Merge branch 'ew/alsa'Eric Wong2008-09-071-78/+69
|\ \ | | | | | | | | | | | | | | | | | | * ew/alsa: alsa: optimistically try resuming from suspend alsa: extra debugging outputs to fix suspend/hibernate alsa: cleanup debug assignment of the "cmd" variable
| * | alsa: optimistically try resuming from suspendEric Wong2008-09-071-11/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apparently snd_pcm_hw_params_can_resume() can return false even though my hardware does in fact support resuming. So stop carrying that value in the canResume flag and just try to resume when we're in the suspended state; falling back to snd_pcm_prepare only if resuming fails. libao does something similar on resume, too. While we're at it, use the E() macro which will enable us to have better error reporting.
| * | alsa: extra debugging outputs to fix suspend/hibernateEric Wong2008-09-071-3/+9
| | | | | | | | | | | | | | | | | | Hibernating my laptop while MPD is playing results in ugliness about "alsa device foo was suspend" constantly printed to the logs.
| * | alsa: cleanup debug assignment of the "cmd" variableEric Wong2008-09-071-66/+50
| | | | | | | | | | | | | | | Given the length of the ALSA command names, I only want to see them once per-section of code, if at all...
* | | playlist: re-randomize when explicitly playing a new songEric Wong2008-09-071-0/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When random is enabled and a user explicitly specifies a certain song on the playlist should be played; we need to re-randomize the internal ordering. To reproduce this, assuming a four song playlist: play <song_a> next => <song_b> next => <song_c> next => <song_d> play <song_a> next => <song_b> next => <song_c> next => <song_d> ... That is, the "next" command restarts song_{b,c,d} the second time "play" starts playing song_a. Thus, the second time "play" is called, the ordering of song_{b,c,d} needs to be reshuffled. Reported-by: Qball
* | tag: oops, of course items is now ** and not *Eric Wong2008-09-051-2/+2
| | | | | | | | | | | | Gah, it seems like doing sizeof here either way is error prone. Too easy to leave out a '*' character we can forget.
* | audio_format: volatile removalEric Wong2008-09-051-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | volatile provides absolutely no guarantee thread-safety in SMP environments. volatile was designed to access memory locations in peripheral hardware directly; not for SMP. If volatile is needed to work properly on SMP, then it is only hiding subtle bugs. volatile only prevents the /compiler/ from making optimizations when accessing variables. CPUs do their own optimizations at runtime so it cannot guarantee registers of CPUs are flushed to memory cache-coherent access on different CPUs. Furthermore, the thread-communication via condition variables between threads sharing audio formats already results in memory barriers.